- -dangerously-skip-reading-code – olano.dev
6 hours ago
- #LLM Engineering
- #Software Process
- #Organizational Change
- The author previously argued that assuming LLMs eliminate the need for reading and debugging code is irresponsible, as programmers remain accountable.
- If organizational leadership accepts the risks and mandates using LLMs to minimize coding time, this becomes a constraint that can redefine engineering practices.
- In such a context, LLM-generated code might be treated like machine code (e.g., assembly or transpiled JavaScript), not requiring direct human reading.
- The Thoughtworks report highlights that LLMs produce non-deterministic output faster than humans can read, making traditional code review impractical.
- Rigor must shift from code review to other areas, such as specifications and tests, with automated checks ensuring code conforms to specs.
- This shift requires organizational changes, not just individual or team decisions, to avoid bottlenecks and realize productivity gains, per Amdahl's law.
- Processes must remove human bottlenecks, reduce coordination, and empower engineers to own entire work streams with autonomous decision-making.
- Rework becomes cheap, so preventing incorrect work is less critical; focus should be on clear specifications and test cases as the primary artifacts.
- A standardized Markdown specification could become the core unit of knowledge, reviewed and maintained by teams, with automated validation against code.