The Knowledge Debt Behind AI Coding
The first change went in fine, and that where this begins. You moved a button, added a field, or fixed the “thing” that had been bothering you since Saturday. You asked for it in plain English, the machine did it, and the screen looked right. It went so smoothly that it seemed to say something reassuring about the software you had built, when what it was actually reporting was how small that software still was.
The second change is the one that breaks something you were nowhere near. A field you never touched stops saving. A page you haven’t opened in a week starts throwing an error. The strange part isn’t the breakage, because software breaks and always has. The strange part is that you have no idea why, and no way to find out that doesn’t involve asking the same machine that wrote the thing in the first place....
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
