I beg to differ. Let's say you're right. Code producers should turn to agriculture and let their managers and product owners prompt AI to produce code. How about code maintainers? Ever heard the mantra "You build it, you run it"? Lets say that AI can build it. Can it run it though? All alone, safely, securely and reliably? No. It can't. We can keep dreaming though, and when will AI code production services turn profitable? Is there a single one which turned profitable?
back
2 comments
There are already agents doing this in SRE roles.
Agents are monitoring metrics and logs. A bug is introduced into the system. Error rates go up and the agents notify diagnostic agents. These agents look at recent commits and figure out the problem. They instruct another agent about how to fix the issue and deploy the change. The problem is fixed before an engineer even has time to start looking at logs.
If you aren’t seeing this, you’re not keeping up with what others are already doing. It’s not just people vibe coding ToDo apps.
Calm down buddy, maybe you're confusing code producers with something else. It's 2026 we don't bother with maintenance no more, we /new to keep context clean and start over.
Just don't forget to comment - never delete - old code. Always keep dead code around to please shareholders, line numbers up always.
We produce code, that is the main thing, never forget.
One could argue we could achieve the same goals by appending \n to a file in a loop, but this is inefficient nowadays with generous token offerings (but could change in the future than I highly suggest just outputting \n to a file an call it productivity increase)
I didn't understand your point about product owners. Who the fuck would ever need one when code produces itself?
Right but memory is expensive now so where do I keep all of this new code that I’ve produced??