←back to thread

Code Is Debt

(tornikeo.com)
118 points tornikeo | 2 comments | 31 Aug 25 17:58 UTC | HN request time: 0s | source
Show context
dkural ◴[31 Aug 25 20:36 UTC] No.45086831[source]▶
So many people are unable to imagine a future where any misunderstandings in execution by the programmer (AI in this case) can be more pleasantly and quickly solved by a conversation between product team / designer / QA and the AI-dev. There are systems in place to prevent junior devs from nuking your systems. Or senior disgruntled / insane devs from nuking your systems. This is why we have db backups, staging, etc. Programming uses a relatively limited vocabulary to talk about a relatively limited number of things. It will be better at the build-feedback-correct loop than 99% of devs. It will remember conversations, detail, everything basically. Just wait a few years. Lines of codes will be as irrelevant as #s of 0s and 1s.
replies(1): >>45086866 #
1. postquantumfax ◴[31 Aug 25 20:40 UTC] No.45086866[source]▶
How long are those conversations between team designer and QA? How many seemingly trivial details have to be discussed over and over because addressing one of them creates an inconsistency in the others? I think this is the debt that can usually be estimated by lines of code.
replies(1): >>45097996 #
2. dkural ◴[02 Sep 25 00:50 UTC] No.45097996[source]▶
It is a lot easier for one unified ML model to remember all the conversations as opposed to a team of engineers who may not communicate with each other anywhere nearing perfect accuracy.