<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tools on dolftax</title>
    <link>https://dolftax.com/tags/tools/</link>
    <description>Recent content in Tools on dolftax</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 04 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://dolftax.com/tags/tools/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The case for moddable software</title>
      <link>https://dolftax.com/posts/case-for-moddable-software/</link>
      <pubDate>Sat, 04 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://dolftax.com/posts/case-for-moddable-software/</guid>
      <description>&lt;p&gt;I enjoy tweaking my tools &amp;ndash; Ghostty, Neovim, tmux, zsh, etc. Keybindings, layouts, little scripts that glue them together. It always took longer than it should, an evening to wire one thing to another, most of it trial and error.&lt;/p&gt;&#xA;&lt;p&gt;What they have in common: everything is a config file. I wrote a custom Gruvbox theme for Ghostty because the built-in palette wasn&amp;rsquo;t quite right. Last week I ripped out my tmux status bar and replaced it with a shell script. Three tools, three text files, talking to each other. Compare that to most commercial software, where customization means a settings panel with a handful of toggles and maybe a theme picker. The developer decided what you need and sealed the rest shut. Config-driven software works the other way around: here&amp;rsquo;s the core, here are the knobs, do what you want. The developer builds a foundation and gets out of the way.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
