Do you let LLMs write both your tests and your code?
Summary
A Lobsters discussion asking whether teams allow LLMs to write both production code and tests, with the author considering a policy restricting AI generation to only one of the two to avoid tautological, over-engineered results.
View Cached Full Text
Cached at: 10/17/26, 02:47 AM
Similar Articles
NLNet Labs LLM Policy
NLNet Labs announces a policy restricting the use of LLMs in code and documentation contributions, requiring disclosure of LLM use and prohibiting AI-generated code.
Your LLM shouldn’t be your coding-agent workflow
Argues that LLMs should be used for reasoning within coding-agent workflows, while deterministic infrastructure handles queues, state, retries, and recovery, so the process doesn't break when usage limits hit.
Will there be 1 and only programming language?
A discussion post arguing that if LLMs write most code, we should design a single AI-oriented language where users describe intent and constraints while the compiler decides implementation details across languages like Go, Java, or SQL.
Anyone NOT on full auto when coding with local LLMs?
The article discusses developers' preferences for full automation versus manual workflows when using local LLMs for coding.
Choose what LLMs can and can’t do well
The article highlights that LLMs excel at ambiguous judgment tasks but are mediocre for consistent computation, advocating for task specialization in multi-agent systems.