<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Devtools - Tag - vo.rs</title><link>https://vo.rs/tags/devtools/</link><description>Devtools - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 20 Jan 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/devtools/" rel="self" type="application/rss+xml"/><item><title>Neovim in 2026: A Practical Setup for People Who Also Have Work to Do</title><link>https://vo.rs/story/neovim-in-2026-a-practical-setup-for-people-who-also-have-work-to-do/</link><description>&lt;p&gt;Neovim has a reputation, and it isn&amp;rsquo;t entirely undeserved: the editor you spend a weekend configuring instead of using. I&amp;rsquo;ve lost those weekends. I&amp;rsquo;ve stayed up until 2am chasing a plugin conflict that turned out to be a load-order problem, and I&amp;rsquo;ve rebuilt my config from scratch more times than I&amp;rsquo;ll admit in writing. I&amp;rsquo;ve also come out the other side with an editor I genuinely prefer to anything else — and the good news, the whole reason for this post, is that in 2026 you no longer have to pay that tax. The ecosystem has matured into a small set of plugins that do the heavy lifting, and a sensible config is now a few hundred lines of readable Lua rather than a haunted 3,000-line &lt;code&gt;init.vim&lt;/code&gt; inherited from a stranger&amp;rsquo;s dotfiles. This is the setup I&amp;rsquo;d hand someone who wants a capable editor and also, crucially, has actual work to do this week.&lt;/p&gt;</description><pubDate>Tue, 20 Jan 2026 09:00:00 +0000</pubDate></item><item><title>Nix: Reproducible Development Environments (Once You Survive the Learning Curve)</title><link>https://vo.rs/story/nix-reproducible-development-environments-once-you-survive-the-learning-curve/</link><description>&lt;p&gt;Every developer has lived the same small tragedy. A new colleague clones the repo, follows the README to the letter, and nothing works. The wrong version of Node. A missing system library. A &lt;code&gt;make&lt;/code&gt; step that needs a tool nobody documented because it&amp;rsquo;s been on the lead&amp;rsquo;s laptop since 2019 and they forgot it wasn&amp;rsquo;t standard. Half a day vanishes into &amp;ldquo;what version of what do you have installed&amp;rdquo;, and the answer, always, is &lt;em&gt;different from mine&lt;/em&gt;. Nix exists to make this entire category of misery go away — and it does, eventually, after putting you through a learning curve I will not pretend is gentle. This post is both the pitch and the warning, because I think the pitch is real and the warning is earned.&lt;/p&gt;</description><pubDate>Tue, 16 Apr 2024 09:00:00 +0000</pubDate></item></channel></rss>