<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Justin Schoenegge</title><link>https://justinschoenegge.com</link><description>Updates from Justin Schoenegge</description><item><title>Reconnecting with an old creative archive</title><link>https://justinschoenegge.com/posts/reconnecting-with-an-old-creative-archive.html</link><guid>https://justinschoenegge.com/posts/reconnecting-with-an-old-creative-archive.html</guid><pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate><description>&lt;p&gt;Currently reconnecting with a legacy creative archive through SSH, revisiting years of original artwork and dormant assets.&lt;/p&gt;
&lt;p&gt;I&#x27;m exploring how emerging AI tools can breathe new life into past projects, transforming forgotten work into fresh creative opportunities.&lt;/p&gt;
&lt;p&gt;Sometimes the next big thing is already sitting on an old hard drive.&lt;/p&gt;</description></item><item><title>Locking down my AI setup</title><link>https://justinschoenegge.com/posts/locking-down-my-ai-setup.html</link><guid>https://justinschoenegge.com/posts/locking-down-my-ai-setup.html</guid><pubDate>Sun, 11 Oct 2026 00:00:00 +0000</pubDate><description>&lt;p&gt;I use Claude Code for almost everything I build here, so I took an evening to check what it&#x27;s actually allowed to do on my Mac.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The audit.&lt;/strong&gt; The basics of how my Mac is set up turned out to be the most important protection. The assistant&#x27;s own allow list was a different story. Months of clicking &quot;always allow&quot; had built up a long list of rules, and some were broader than I&#x27;d meant them to be.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A password check for risky commands.&lt;/strong&gt; Instead of trimming the list right away, I added a hook: a small script that runs before every shell command. If a command looks like it could compromise the machine, a dialog asks for my password first, and Cancel blocks it. I tested it against risky and everyday commands until it caught the first without getting in the way of the second. It&#x27;s a safety net, not a wall.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Rotating a key.&lt;/strong&gt; My stock chart project uses an Anthropic API key, and that key had ended up in a session transcript. It came up again during this cleanup, so I rotated it: made a new key, pasted it straight into the local secrets file (never into chat), and tested it with a check that only shows a status code.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Takeaways&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Get the basics of your computer&#x27;s setup right. They do more than any tool you add on top.&lt;/li&gt;
&lt;li&gt;&quot;Always allow&quot; adds up. Review the list every so often.&lt;/li&gt;
&lt;li&gt;Secrets go into files by hand, never through chat or the terminal. Even a redaction filter can fail without telling you.&lt;/li&gt;
&lt;li&gt;When a key might have leaked, rotating it is cheap and settles the question.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Rebuilding this site</title><link>https://justinschoenegge.com/posts/rebuilding-this-site.html</link><guid>https://justinschoenegge.com/posts/rebuilding-this-site.html</guid><pubDate>Sat, 10 Oct 2026 00:00:00 +0000</pubDate><description>&lt;p&gt;The old version of this site was a template with a few travel photos — and a broken email link.
I&#x27;m turning it into a running log instead: a page for each project, and short updates as I work on them.&lt;/p&gt;
&lt;p&gt;Most of what I build is small and personal. Writing it down here is a way to see it add up.&lt;/p&gt;</description></item></channel></rss>