108 PRs in Eight Days: Accidentally Discovering Loop Engineering
I recently shipped 108 pull requests in eight days by implementing a loop engineering system with an AI agent. Instead of line-by-line reviews, my team shifted to outcome-based testing, allowing rapid iteration while maintaining quality. This approach moved my focus from writing code to defining specs and verifying results, proving that human effort is now the bottleneck in the pipeline.
It almost feels like being a software engineer in 2026 is just being a product manager and QA.
- scottydelta
From the article
> We also don't have continuous deployment (CD) set up. That's a weird thing for me to say as a positive, because for a very long time that was a hallmark of good software engineering practices... but with me shipping 108 PRs in a week, I actually have been thinking differently.
It’s still a hallmark of good software engineering.
- calldacopsidgaf
We are past the point where these claims are impressive, anyone can open a shitload of PRs with AI.
It's the context around review, safety, etc that might make your headline interesting, but unfortunately i have no way of seeing that because the website times out.
- xnx
PR count matters as much/little as lines of code count.