<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Productivity on Tom Meurs</title>
    <link>https://tommeurs.nl/en/categories/productivity/</link>
    <description>Recent content in Productivity on Tom Meurs</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© Tom Meurs</copyright>
    <lastBuildDate>Wed, 03 Jun 2026 21:17:00 +0100</lastBuildDate>
    <atom:link href="https://tommeurs.nl/en/categories/productivity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>KVM/QEMU Scripts and Aliases: Making Virtualization Actually Usable</title>
      <link>https://tommeurs.nl/en/posts/kvm-qemu-scripts-aliases/</link>
      <pubDate>Wed, 03 Jun 2026 21:17:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/kvm-qemu-scripts-aliases/</guid>
      <description>&lt;p&gt;I run VMs all day. A Kubernetes deployment I want to test, a distro I read about, Windows for that one stubborn application, an experiment I&amp;rsquo;d rather not run on my actual machine. KVM/QEMU is the right tool for all of it. It lives in the Linux kernel and runs close to native speed. Nothing in it phones home, and no vendor gets a say in what I do with my own hardware.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Terminal Multiplexing: tmux vs Zellij vs Screen</title>
      <link>https://tommeurs.nl/en/posts/terminal-multiplexing/</link>
      <pubDate>Thu, 14 May 2026 19:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/terminal-multiplexing/</guid>
      <description>&lt;p&gt;The first time it bit me I was halfway through a database migration over SSH. The train went into a tunnel, the WiFi dropped, and the process on the other end died with the connection. I sat looking at a dead prompt, wondering how much of the migration had committed.&lt;/p&gt;&#xA;&lt;p&gt;A multiplexer would have saved me that hour. The process keeps running on the server whether I&amp;rsquo;m attached or not, so a dropped connection costs me a reconnect and nothing else. I reattach and the work is where I left it. That one property is why a multiplexer goes on every machine I touch, before the editor and before the dotfiles.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Lost Art of Software Optimization: What Demoscene Taught Us About Sustainability</title>
      <link>https://tommeurs.nl/en/posts/demoscene-optimization-sustainability/</link>
      <pubDate>Sat, 07 Mar 2026 20:42:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/demoscene-optimization-sustainability/</guid>
      <description>&lt;p&gt;Most of us ship software the same way now. Pick a framework, pull in a few hundred dependencies, and the service idles at a gigabyte of RAM before it does its first useful piece of work. Nobody profiles it. If it&amp;rsquo;s slow, you scale up. Compute is cheap, your time isn&amp;rsquo;t, and the bill goes to someone else. I don&amp;rsquo;t say that as a complaint. I&amp;rsquo;ve done it, and I&amp;rsquo;ll do it again on the next deadline.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Learn the Defaults: Why Portability Beats Customization</title>
      <link>https://tommeurs.nl/en/posts/learn-the-defaults/</link>
      <pubDate>Sun, 15 Feb 2026 19:47:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/learn-the-defaults/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; I spent years polishing a vim and tmux setup, then sat useless in front of a stock vim on a production server. So I learned the defaults I&amp;rsquo;d been overriding all along, and moved my customizations on top of them instead of in place of them. What that looks like for vim, tmux and the shell tools, and the four checks I use to find the gaps.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;For years my setup was the thing I was proudest of. A dotfiles repo with commits going back further than some of my jobs, a vim config that pulled in thirty plugins, the tmux prefix moved somewhere comfortable, a prompt that took a weekend to get right. Down to the last keybinding, it was mine. On my laptop I was fast, and I hardly thought about the tools at all. Muscle memory did the work.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dotfile Management with mise and chezmoi: The Perfect Combo</title>
      <link>https://tommeurs.nl/en/posts/dotfile-management-mise-chezmoi/</link>
      <pubDate>Wed, 11 Feb 2026 20:23:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/dotfile-management-mise-chezmoi/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; Six ways of syncing dotfiles later, the one I kept is chezmoi for the files and mise for the tool versions, with the mise config living inside the chezmoi repo. Templates handle the work laptop against the personal desktop, age handles the secrets, and a fresh machine is one command and about five minutes. The walk-through goes from one managed file to the bootstrap I run for real.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;My &lt;code&gt;.zshrc&lt;/code&gt; is older than some of my coworkers&amp;rsquo; careers. Same for my &lt;code&gt;.vimrc&lt;/code&gt; and my tmux config. They&amp;rsquo;ve grown into a setup that does exactly what I want, and I&amp;rsquo;d be lost without them. The catch is that I run more than one machine. A laptop, a desktop, now and then a throwaway VM for testing. For years, keeping those in sync was a pile of hacks I didn&amp;rsquo;t trust.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The space container thought experiment: systems thinking for survival</title>
      <link>https://tommeurs.nl/en/posts/spaceship-thought-experiment/</link>
      <pubDate>Tue, 20 Jan 2026 14:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/spaceship-thought-experiment/</guid>
      <description>&lt;p&gt;You wake up. It&amp;rsquo;s dark. Somewhere a fan is humming.&lt;/p&gt;&#xA;&lt;p&gt;Your eyes adjust. You&amp;rsquo;re in a container. Metal walls, a few small windows, and behind them stars. Just stars. No Earth anywhere.&lt;/p&gt;&#xA;&lt;p&gt;There&amp;rsquo;s a note taped to the wall:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;&amp;ldquo;You have everything you need to survive. Nothing goes in, nothing goes out. Good luck.&amp;rdquo;&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;I bring this one up with friends when the evening has gone quiet enough for it. It sounds like science fiction, and the first reaction is usually a joke about the toilet. Then somebody asks what&amp;rsquo;s in the room, and we&amp;rsquo;re off. What the experiment takes away is an assumption I&amp;rsquo;d never said out loud before I ran it. That there&amp;rsquo;s an &amp;ldquo;outside&amp;rdquo; that absorbs my mistakes and refills my supplies.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taskwarrior, Timewarrior and Vit: The Ultimate CLI Productivity Stack</title>
      <link>https://tommeurs.nl/en/posts/taskwarrior-timewarrior-vit-tutorial/</link>
      <pubDate>Sat, 03 Jan 2026 15:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/taskwarrior-timewarrior-vit-tutorial/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; Taskwarrior, timewarrior and vit are my task list, my time tracking and the vim-style screen on top, all in the terminal and all plain text in &lt;code&gt;~/.task&lt;/code&gt;. Two commands get you started. The rest of this post is what I bolted on afterwards, from projects and dependencies to a self-hosted sync server, and you can stop at any section.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;For context on how my brain works, see &lt;a href=&#34;https://tommeurs.nl/en/posts/working-with-audhd-brain/&#34;&gt;Working with an AuDHD Brain&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Working with an AuDHD brain: why I automate everything</title>
      <link>https://tommeurs.nl/en/posts/working-with-audhd-brain/</link>
      <pubDate>Sat, 27 Dec 2025 14:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/working-with-audhd-brain/</guid>
      <description>&lt;p&gt;For a long time I thought the problem was me.&lt;/p&gt;&#xA;&lt;p&gt;I have &lt;span class=&#34;def&#34; tabindex=&#34;0&#34; data-def=&#34;Autism combined with ADHD. The author has the inattentive presentation of ADHD, and writes about what that means for infrastructure work rather than about the diagnosis.&#34;&gt;AuDHD&lt;/span&gt;&#xA;, autism and ADHD together. The ADHD is ADHD-PI, the inattentive kind, without the hyperactivity most people picture when they hear the word. For years I treated the whole thing as a defect I&amp;rsquo;d train away. I bought the planners. I read the productivity books. Every week I told myself that Monday I&amp;rsquo;d finally be disciplined.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
