| ▲ | apical_dendrite 14 hours ago | |
We're currently wasting a lot of time cleaning up slop created by overusing AI. The loop is: developer uses AI to create a huge amount of code very quickly. But the developer didn't understand the underlying system very well so the specs generated by the AI contain a lot of faulty assumptions and the code was then built on those assumptions. So you have features that probably shouldn't have existed in the first place, but because they do exist people have provided feedback on them, and the developer then uses the AI to implement that feedback, but still doesn't understand the system so much of the code for the revisions is still wrong. So that individual developer saw a huge productivity increase, in the sense that he generated a vast amount of code really quickly, but the team as a whole saw a productivity decrease. | ||
| ▲ | CuriouslyC 2 hours ago | parent [-] | |
Ironic plot twist, AI is just exposing your coworker's weakness. They could slow down and understand before blasting away at code, or explicitly hang back and generate tech demos/PoCs for architectural choices while building understanding, but they didn't. The only reason things were ok before was because they were handicapped to a speed slower than their ability to figure things out. | ||