<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Jeff Bailey | Developer Tools</title><link>https://jeffbailey.us/categories/developer-tools/</link><description>This website contains learning resources, opinions, and facts about software-related technology.</description><language>en</language><generator>Hugo</generator><atom:link href="https://jeffbailey.us/categories/developer-tools/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Sat, 25 Apr 2026 00:00:00 +0000</lastBuildDate><item><title>What Is fzf?</title><link>https://jeffbailey.us/blog/2026/04/25/what-is-fzf/</link><guid isPermaLink="true">https://jeffbailey.us/blog/2026/04/25/what-is-fzf/</guid><pubDate>Sat, 25 Apr 2026 00:00:00 +0000</pubDate><dc:creator>Jeff Bailey</dc:creator><category>Developer Tools</category><category>Productivity</category><category>Command Line</category><description><![CDATA[<p>I used to open files the slow way: <code>cd</code> into a directory, <code>ls</code> to see what&rsquo;s there, maybe <code>find</code> with a half-remembered filename, then pass it to whatever program I needed. Every time, I&rsquo;d lose a few seconds hunting for the right path. Multiply that by dozens of files a day, and it adds up to real friction.</p>
<p>Then I found fzf, and file selection stopped being a chore. fzf is a fuzzy finder that turns file selection into a fast, interactive search.</p>]]></description></item><item><title>What Is Zoxide?</title><link>https://jeffbailey.us/blog/2026/04/21/what-is-zoxide/</link><guid isPermaLink="true">https://jeffbailey.us/blog/2026/04/21/what-is-zoxide/</guid><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><dc:creator>Jeff Bailey</dc:creator><category>Developer Tools</category><category>Productivity</category><category>Command Line</category><description><![CDATA[<p>I used to navigate my filesystem one directory at a time. <code>cd ~/Projects</code>, then <code>ls</code>, then <code>cd websites</code>, then <code>ls</code>, then <code>cd jeffbaileyblog</code>, then <code>ls</code>, then <code>cd hugo</code>. Every trip to a familiar directory cost me four or five commands. Tab-completion helped a little, but I still had to remember the path.</p>
<p>Then I installed zoxide, and <code>cd</code> started reading my mind.</p>
<h2 id="what-zoxide-actually-is">What zoxide actually is</h2>
<p>Zoxide is a smarter replacement for <code>cd</code>. It watches where you go in your terminal, ranks those directories by how often and how recently you visit them, and lets you jump to any of them by typing a fragment of the path.</p>]]></description></item><item><title>What Is Claude Code?</title><link>https://jeffbailey.us/blog/2026/04/21/what-is-claude-code/</link><guid isPermaLink="true">https://jeffbailey.us/blog/2026/04/21/what-is-claude-code/</guid><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><dc:creator>Jeff Bailey</dc:creator><category>Developer Tools</category><category>AI</category><category>Productivity</category><description><![CDATA[<p>For years, &ldquo;AI in my editor&rdquo; meant autocomplete. Copilot would suggest the next few tokens, I&rsquo;d hit tab, and that was the interaction. Useful, but shallow. The AI stayed in one file, ignored my tests, and had no way to know when its suggestion broke the build.</p>
<p>Claude Code works at a different level. It runs in my terminal, reads my files, runs my commands, and talks back in plain language. When I ask it to fix a failing test, it runs the test, reads the failure, finds the bug, edits the file, and runs the test again to confirm. The result feels less like autocomplete and more like delegating a small task to a teammate.</p>]]></description></item></channel></rss>