<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scott Berrevoets - Developer Tools</title><link>https://scottberrevoets.com/</link><description/><atom:link href="https://scottberrevoets.com/feeds/developer-tools.rss.xml" rel="self"/><lastBuildDate>Wed, 01 Jul 2026 00:00:00 -0700</lastBuildDate><item><title>How GitHub handles Git LFS</title><link>https://scottberrevoets.com/2026/07/01/how-github-handles-git-lfs/</link><description>&lt;p&gt;Snapshot tests have become an increasingly popular tool for mobile
teams to verify UI changes, but one question all teams run into is: where
do we store hundreds if not thousands of PNG files? Git Large File Storage
(LFS) is one of the more common ways to do this for …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Wed, 01 Jul 2026 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2026-07-01:/2026/07/01/how-github-handles-git-lfs/</guid><category>Developer Tools</category><category>Testing</category><category>Developer Experience</category></item><item><title>Scaling my git/tmux workflows for AI agents</title><link>https://scottberrevoets.com/2026/02/17/scaling-my-gittmux-workflows-for-ai-agents/</link><description>&lt;p&gt;After I started to ramp up on agentic coding, I found my workflow lagging behind
how I ended up working. Previously I would clone my project's repo twice and
switch back and forth between the clones. I used stack-based git workflow
&lt;a href="https://github.com/keith/git-pile"&gt;git-pile&lt;/a&gt;, which eliminated the overhead of switching branches and …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Tue, 17 Feb 2026 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2026-02-17:/2026/02/17/scaling-my-gittmux-workflows-for-ai-agents/</guid><category>Developer Tools</category><category>Developer Experience</category></item><item><title>Composing a resume in markdown</title><link>https://scottberrevoets.com/2025/03/15/composing-a-resume-in-markdown/</link><description>&lt;p&gt;I recently updated my resume, and after a few iterations of tweaking the same
Pages file I started more than a decade ago, I decided that I really wanted
source control to make it easier to keep track of changes and to have different
versions of the same resume. Additionally …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Sat, 15 Mar 2025 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2025-03-15:/2025/03/15/composing-a-resume-in-markdown/</guid><category>Developer Tools</category><category>Developer Experience</category></item><item><title>Looking up words in a dictionary with Neovim</title><link>https://scottberrevoets.com/2024/12/08/looking-up-words-in-a-dictionary-with-neovim/</link><description>&lt;p&gt;When writing code in neovim, I frequently use &lt;code&gt;K&lt;/code&gt; to look up documentation,
function signatures, variable definitions, etc. In markdown files that doesn't
make too much sense, but I wanted to use it to look up words in the dictionary
instead. This didn't appear to be possible out of the …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Sun, 08 Dec 2024 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2024-12-08:/2024/12/08/looking-up-words-in-a-dictionary-with-neovim/</guid><category>Developer Tools</category><category>Developer Experience</category></item></channel></rss>