Comment by lionkor
14 hours ago
None of these are things I want or need in the product I maintain with a team, there's really no point to any of this unless you run a vibe coded SaaS (?)
14 hours ago
None of these are things I want or need in the product I maintain with a team, there's really no point to any of this unless you run a vibe coded SaaS (?)
Your non-vibecoded non-SaaS application never has errors?
You want your team spending their time fixing these simple errors? The secret sauce is in the triage. We've adopted solutions alot like this, and now our team spends its time on much more meaningful work.
Why are the errors occurring, though? That's what boring analyse-and-fix addresses, through familiarity, recognition of patterns and "hang onnn..." moments.
It's like your AI agent is just plugging the leaks in the dyke each time, instead of fixing the architecture of the dam.
There are many sources of boring predictable errors which nonetheless are easy to miss and easy to fix. API validation errors for example.
Yes, I want my team to be deeply familiar with the codebase and every single little bug that needs fixing both trains them and let's them learn a little bit more about the codebase.
They can use agents. Like, team members don't need to be replaced, they can simply use agents when they deem it useful. If they see a trivial bug,they can put their agent on it and go work on something else meanwhile.