Egregoros

Signal feed

Timeline

Post

Remote status

Context

1

If you replace a junior with #LLM and make the senior review output, the reviewer is now scanning for rare but catastrophic errors scattered across a much larger output surface due to LLM "productivity."

That's a cognitively brutal task.

Humans are terrible at sustained vigilance for rare events in high-volume streams. Aviation, nuclear, radiology all have extensive literature on exactly this failure mode.

I propose any productivity gains will be consumed by false negative review failures.

Replies

2
@pseudonym really smells like a problem caused by lack of TDD more than anything else

Maybe other languages need to get up to Elixir/Erlang's level.

- force warnings as errors
- write the tests
- make it write the code to pass them
- make it use typespecs on all the public functions
- make it pass credo checks (gigantic list of code smells)
- make it pass dialyzer (zero false positives possible, detects dead/unreachable code too)

now you've got bug free code unless you screwed up and have logic errors in your design.