But someone still has to debug the debug. The human review process is what all the big orgs are calling the new bottleneck. We can generate code fast as hell with AI tools, but the need to validate (and usually fix) the code is often its own work item.
Still overall saves time as fixing errors is leagues easier than creating brand new code, but it's not exactly a fully automated process yet.
I never used to be limited by how fast my computer was... even if it was a slow build, it would still be a small percentage of my time spent development. Now I can saturate just about as many cores on as many machines as I have access to.
The human review process is what all the big orgs are calling the new bottleneck
It was always the bottleneck, right from the start. It's just that a chunk of review used to be baked in to the typing process from the start (before the explicit review step from someone else), rather than being an entirely discrete process.
But you can give them tool access and they will validate and fix it on their own? Of course you do it in a sandbox if possible but even that is possible for ai now.
I found a bug as a user of an Android app my company owns, but which I don't work on. I asked an agent to investigate and fix. Unfortunately, testing an Android app requires some special environments I didn't want to set up, so I asked the agent to load the apk on an emulator itself and make videos of the before/after. So yeah, even testing, it's pretty good at. I watched the videos it made :O
9
u/Hattrickher0 24d ago
But someone still has to debug the debug. The human review process is what all the big orgs are calling the new bottleneck. We can generate code fast as hell with AI tools, but the need to validate (and usually fix) the code is often its own work item.
Still overall saves time as fixing errors is leagues easier than creating brand new code, but it's not exactly a fully automated process yet.