<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ai-Drafted on taude.xyz</title><link>http://taude.xyz/tags/ai-drafted/</link><description>Recent content in Ai-Drafted on taude.xyz</description><generator>Hugo</generator><language>en-us</language><copyright>Todd</copyright><lastBuildDate>Tue, 15 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://taude.xyz/tags/ai-drafted/index.xml" rel="self" type="application/rss+xml"/><item><title>Skip Ollama, Run llama.cpp Directly on a Mac</title><link>http://taude.xyz/posts/skip-ollama-run-llama-cpp-directly-on-a-mac/</link><pubDate>Tue, 15 Sep 2026 00:00:00 +0000</pubDate><guid>http://taude.xyz/posts/skip-ollama-run-llama-cpp-directly-on-a-mac/</guid><description>&lt;p&gt;&lt;em&gt;Prompted by an HN thread: &lt;a href="https://news.ycombinator.com/item?id=47788385"&gt;The Local LLM Ecosystem Doesn&amp;rsquo;t Need Ollama&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Ollama is built on llama.cpp. For more than 400 days it ignored a GitHub issue asking it to say so. That&amp;rsquo;s the headline complaint in a recent Hacker News thread — but the more useful finding, buried underneath, is that llama.cpp no longer needs a wrapper at all. On a Mac it&amp;rsquo;s now the simpler choice, not the harder one.&lt;/p&gt;</description></item><item><title>Auditing my own scripts drawer</title><link>http://taude.xyz/posts/auditing-my-own-scripts-drawer/</link><pubDate>Thu, 03 Sep 2026 17:53:00 -0400</pubDate><guid>http://taude.xyz/posts/auditing-my-own-scripts-drawer/</guid><description>&lt;p&gt;Every developer has a &lt;code&gt;~/dev/tools/scripts&lt;/code&gt; folder. Mine has run for years
without an index. I asked Claude Code to read every file in it and write
one.&lt;/p&gt;
&lt;p&gt;The brief was simple: read the whole directory, then produce an &lt;code&gt;INDEX.md&lt;/code&gt;
with three columns — tool, how to run it, what it does.&lt;/p&gt;
&lt;p&gt;It scanned roughly 40 files: Python CLIs built on &lt;code&gt;uv&lt;/code&gt;, shell wrappers, one-off
Snowflake key-rotation scripts, a tmux session launcher, a Hacker News
summarizer. Some had docstrings. Several had none, and their purpose was
recoverable only by reading the &lt;code&gt;argparse&lt;/code&gt; block or the hardcoded constants
at the top.&lt;/p&gt;</description></item><item><title>Local Dev Secret Management with 1Password and Bitwarden</title><link>http://taude.xyz/posts/local-dev-secret-management-with-1password-and-bitwarden/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><guid>http://taude.xyz/posts/local-dev-secret-management-with-1password-and-bitwarden/</guid><description>&lt;p&gt;Most developers have a graveyard of dotfiles, &lt;code&gt;.env&lt;/code&gt; files, and Slack DMs containing tokens that were supposed to be temporary. This post describes the pattern I use to keep all local dev secrets in a password manager and inject them into my shell on demand — nothing sensitive ever touches disk.&lt;/p&gt;
&lt;p&gt;The full setup lives in my &lt;a href="https://github.com/taudep/dot-local"&gt;dot-local repo on GitHub&lt;/a&gt;, including the helper functions and new-machine setup guide.&lt;/p&gt;
&lt;h2 id="the-problem"&gt;The Problem&lt;/h2&gt;
&lt;p&gt;I work across multiple machines: a work Mac that uses 1Password and a personal Mac that uses Bitwarden. I needed a single pattern that worked on both without maintaining two separate codebases or hardcoding tool-specific logic everywhere.&lt;/p&gt;</description></item></channel></rss>