Pull Request now means Pull & Test

A Not-So Biblical Flood of PRs How many tickets are you completing a day now? Crushing 20 PRs across 13 repos with no end in sight? An (exaggerated) developer's job has changed. Now a single team member with a modest budget produce a flurry of PRs and keeping up increasingly feels like a fools errand. And with the $/task frontier falling every day (ahem OpenAI and DeepSeek), this is a problem that isn't going to ease down any time soon. Facing a thousand foot wall, what does a thousand and one foot ladder look like? Visual Proof of Success Having built and run an agent orchestration system first hand (and wandered into that dark abyss), I am increasingly convinced that engineering teams are going to settle on systems that produce visual representations of the what a task should produce. It can take all different shapes; pictures of terminals for proof of CLI changes. Chromium snapshots of website updates. Videos of multi-screen workflow changes. But this empowers an engineer (or not!)…