<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Workflow on Severin Bucher | Blog</title><link>https://severinbucher.com/tags/workflow/</link><description>Recent content in Workflow on Severin Bucher | Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 27 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://severinbucher.com/tags/workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop Submitting Giant PRs Nobody Wants to Review</title><link>https://severinbucher.com/posts/stop-submitting-giant-prs-nobody-wants-to-review/</link><pubDate>Fri, 27 Feb 2026 00:00:00 +0000</pubDate><guid>https://severinbucher.com/posts/stop-submitting-giant-prs-nobody-wants-to-review/</guid><description>&lt;p>You know that feeling when you open a PR and it&amp;rsquo;s 47 files changed, 3,000 lines? The reviewer sighs, skims it, leaves a comment like &amp;ldquo;looks good,&amp;rdquo; and merges it. No real feedback, nothing caught. That isn&amp;rsquo;t code review, it&amp;rsquo;s rubber-stamping.&lt;/p>
&lt;p>Stacked PRs are a way out of that trap.&lt;/p>
&lt;h2 id="the-basic-idea">The Basic Idea&lt;/h2>
&lt;p>Instead of one massive PR, you break the work into a chain. Each branch builds on the previous one, and each PR targets its parent branch rather than master directly.&lt;/p></description></item><item><title>A Practical Terminal-Based Development Environment</title><link>https://severinbucher.com/posts/a-practical-terminal-based-development-environment/</link><pubDate>Sun, 19 Oct 2025 00:00:00 +0000</pubDate><guid>https://severinbucher.com/posts/a-practical-terminal-based-development-environment/</guid><description>&lt;p>Most development sessions start with the same chore: bring up the backend, start the frontend build, open the database, get version control where you can see it. Before any actual work happens, a few minutes go to setting up the workspace.&lt;/p>
&lt;p>My setup gets rid of that. It runs almost entirely in the terminal, using tmuxp to build the session and a handful of tools for editing, file management, and version control. Once it&amp;rsquo;s configured, starting work is one command.&lt;/p></description></item></channel></rss>