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.
i finally found this picture again. it has infected me memetically a long time ago
Never touch the terminals.
Please don't. Cause of failure.
This may be the cause.
It is not possible to use multiple computers at the same time.
It is not possible.
Package managers keep using git as a database, it never works out.
https://nesbitt.io/2025/12/24/package-managers-keep-using-git-as-a-database.html
A software engineer without "soft skills" is 0.1x engineer.
We all know this guy.
The one that you make sure to never talk to customer. The one you always need to ensure you approach carefully. The one who's "not good with people."
Yeah, that guy.
Software engineering is fundamentally a team sport. Even if he is very fast at typing in and recalling algorithms from memory, he'll make the entire org around him 1/10 as effective.
@Tattie I often use this when trying to explain LLMs to people