Su-Sheethis is an interesting article about LLM generated code (an sqlite rewrite in rust) and the difference between "it works" and "it's good". also interesting database stuff :)
https://blog.katanaquant.com/p/your-llm-doesnt-write-correct-code
hajovonta@sushee This sentence is probably the most important in the article: "My conclusion is that LLMs work best when the user defines their acceptance criteria before the first line of code is generated."
I put together an IRC server for CL with TDD methodology. For a project this size, I found this is what works best.
arclight@hajovonta @sushee What's been really infuriating about the uptake of agentic coding is the (re)discovery of software engineering principles like proper design documentation, specification, and acceptance testing. We've known the importance of all these things since the 60s and 70s but typically don't spend time on them because coding is (was?) more enjoyable, writing about the code was perceived as less valuable than implementing the code, and having a formal structured process was suffocating, Legacy, and not 'agile' enough.
Nobody would write out this critical information for human use but devs are suddenly overjoyed to write it all down now that they have expensive obsequious incompetent plagiarizing coding robots.
It's like every episode of The Simpsons with Homer being an idiot and doing the right thing for all the wrong reasons.
There's so much anti-humanity bundled up in the commercial LLM space, it's infuriating and depressing.
@arclight
Yeah, actually writing the code is the boring stuff, mostly mechanical and error-prone. I did it for decades. Having a tool doing this part is great, because we can focus on what is more enjoyable: coming up with ideas, planning, setting up scope, providing oversight, controlling the process from a higher level, verifying results.
It is not everyone's cup of cake, I get that. It's not that it takes away the possibility of writing code by hand.