Data fitter Kim retweetledi

I see a new form of tech debt coming for dev teams -
Comprehension debt.
As more and more code is generated by LLMs, if teams don’t take the time to understand deeply what the generated code is doing, as well as code they write by hand…
It’s only a matter of time before the code base starts looking unfamiliar to most of the team.
It then becomes harder to discern if new code that LLMs generate is adding more spaghetti or if there’s a better approach.
It’s a downward spiral from there - unrelated things break with every change despite existing tests passing, no one knows the full picture to be able to fix the root cause, not even an LLM, etc.
So as tempting as it is to move super fast with LLMs, there’s only so much comprehension debt you can rack up before your code base silently becomes a Rube Goldberg machine under your nose.
English












