Workflow

You know that feeling when you open a PR and it’s 47 files changed, 3,000 lines? The reviewer sighs, skims it, leaves a comment like “looks good,” and merges it. No real feedback, nothing caught. That isn’t code review, it’s rubber-stamping. Stacked PRs are a way out of that trap. The Basic Idea 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. ...

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. 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’s configured, starting work is one command. ...