←back to thread

Code Is Debt

(tornikeo.com)
118 points tornikeo | 1 comments | | HN request time: 0s | source
Show context
drooby ◴[] No.45086189[source]
Terse, poorly named variables, and clever code is worse than verbose, well documented, thoroughly named variables with readable dsl.

Debt is proportional to the time it takes to understand, change, and extend the codebase.

Lines of code are an imperfect mapping to tech debt. And if all things truly were equal then this metric has been minimized at the expense of readability - which almost certainty impacts debt worse.

So I think the better argument here is that, "lack of theory is debt" - so ironically, perhaps the better argument is the shorter codebase is debt in the analogy to LLMs. LLM usage minimizes theory building. But this is assuming that AI doesn't continue to progress and its ability to build theory about the project (and communicate it correctly to the engineer) remains constrained.

replies(3): >>45086506 #>>45086542 #>>45086731 #
AlienRobot ◴[] No.45086542[source]
That gave me an idea. Is it possible to ask an AI what a variable/function does in a piece of code? I've only ever used them for generation.
replies(5): >>45086580 #>>45086590 #>>45086634 #>>45086828 #>>45086965 #
1. mceachen ◴[] No.45086965[source]
You can, but with Claude, be sure to watch what files it reads—I’ve seen close to entirely incorrect analysis due to shallow/lazy reading.

If you think it’s phoning it in, tell them to study upstream and downstream consumers, consider edge and corner cases, and what assertions any tests are making of the code in question, and to redo their analysis.