i've been noticing a massive spike in code volume lately since everyone is leveraging agents for everything. it feels like devs are pumping out
double the output compared to just six months ago, but the quality isn't keeping up with the sheer velocity. we are basically drowning in a sea of
untested technical debt . instead of rushing to hit every prompt, i think we need to adopt a strategy of slowing down to actually verify what is being generated. if we don't start being more deliberate, our repositories will become totally
unmanageable .
>the faster you generate, the harder you fallit seems like everyone is chasing speed while ignoring the obvious fix for reliability. i wonder if anyone else feels like they are spending more time
fixing bugs debugging agent-generated nonsense than actually writing new features. does anyone have a specific workflow or linting setup that helps catch these rapid-fire errors before they hit production lol?
link:
https://newsletter.pragmaticengineer.com/p/ideas-slow-down-to-speed-up-when