News for hackers. Stuff that matters.
Re:The L in "LLM" Stands for Lying by wilg on Thursday March 05, 2026 @02:43AM (#47258798)
LLMs are pretty cool technology and are useful for programming.
Re:The L in "LLM" Stands for Lying by emsign on Thursday March 05, 2026 @03:04AM (#47258938)
If you check the code afterwards. You do check the code yourself, don't you?
Re:The L in "LLM" Stands for Lying by malka1986 on Thursday March 05, 2026 @03:36AM (#47259164)
Hello, I am a single dev using an agent (Claude Code) on a solo project.

I have accepted that reading 100% of the generated code is not possible.

I am attempting to find methods to allow for clean code to be generated none the less.

I am using extremely strict DDD architecture. Yes it is totally overkill for a one man project.

Now i only have to be intimate with 2 parts of the code:

* the public facade of the modules, which also happens to be the place where authorization is checked.

* the orchestrators, where multiple modules are tied together.

If the inners of the module are a little sloppy (code duplication and al), it is not really an issue, as these do not have an effect at a distance with the rest of the code.

I have to be on the lookout though. It happens that the agent tries to break the boundaries between the modules, cheating its way with stuff like direct SQL queries.

Re:The L in "LLM" Stands for Lying by EugeneOZ on Thursday March 05, 2026 @04:08AM (#47259395)
I do, 100%, every line.
Re:The L in "LLM" Stands for Lying by wilg on Thursday March 05, 2026 @03:34AM (#47259144)
eyeroll
Re:The L in "LLM" Stands for Lying by PunchyHamster on Thursday March 05, 2026 @04:48AM (#47259707)
No, that would limit our velocity, we can't check code, that eats into the LLM gains