This is true.

I have always prided myself on writing concise, high-Quality code, because it tends to be quite debt-free.

So far, LLMs seem to deliver code with "Louie Da Loan Shark"-levels of tech debt.

mullingitover 3 hours ago | parent | next [-]

The problem is that the lines of code are riding on a stack of other dependencies that all need care and feeding. Things reach EOL. Frameworks have major breaking changes. CVEs are discovered.

▲

bluefirebrand 2 hours ago | parent | prev | next [-]

You mentioned in another part of this thread that you worked in hardware mostly?

It seems like the cost of changing hardware code is high enough to still insist on building it high quality, is that accurate?

	▲	ChrisMarshallNY an hour ago \| parent [-]
		Yes. It's also why working as a software (host) developer at a hardware company is difficult. Hardware people insist on treating software the same as firmware. Bad firmware can cause real-world, physical damage, and be impossible to fix without a hardware recall. A firmware bug can wipe out a hardware company. A software bug can be embarassing, but can also be corrected a lot more easily (as long as it is being treated differently from firmware).

▲

KerrAvon 4 hours ago | parent | prev [-]

You can actually get high-quality code out of them -- at least with Claude; not had a great experience with Gemini -- but for complex tasks requires riding them very, very hard and really understanding where things can go wrong and poking at them repeatedly. Iterate, iterate, iterate.

	▲	ChrisMarshallNY 4 hours ago \| parent [-]
		> Iterate, iterate, iterate. That describes my last week. What made it most annoying, was the need to release through TestFlight, because the memory issues would not appear, when tethered. Also, I was checking in constantly, because I had to revert and reset the context, several times.