Oh right, I keep forgetting about those useful-but-historically-mentally-draining-to-update sources of truth. This might be extremely useful when paired with an agent.
My theory is that most problem solvers are bad at solving problems, and most managers are bad at managing, and it doesn't matter how evolution created them: They'll make mistakes, they'll have finite time and energy, a finite context window, they'll lie and internally rewrite their own internal narratives as needed, and forget things, and drop balls, and they'll go in circles trying to find a bug they created but are too close to be able to see, and they're going to need a lot of external tooling to get through the day without forgetting anything, and constant reminders from others to get shit done. And this dynamic fundamentally creates peaks and valleys in productivity.
Wait, were we talking about humans or AI?
...
Everyone seems to be assuming either the humans or the AI has to be special. What if neither are?
No, AI wasn't supposed to solve all that drudgery. The hypothesized AI singularity would, but an ordinary AI agent running an LLM is just a problem solving automaton with no will of its own, just like a fleshy brain solving computer problems is just a code monkey.
Time is finite and regression testing always gets punted to the back of the line when humans are excited. This simply reveals a staggering level of humanity.
The endgame in programming is reducing complexity before the codebase becomes impossible to reason about. This is not a solved problem, and most codebases the LLMs were trained on are either just before that phase transition or well past it.
Complexity is not just a matter of reducing the complexity of the code, it's also a matter of reducing the complexity of the problem. A programmer can do the former alone with the code, but the latter can only be done during a frank discussion with stakeholders.
A vibe coder using an LLM to generate complexity will not be able to tell which complexity to get rid of, and we don't have enough training data of well-curated complexity for LLMs to figure it out yet.
I agree with everything you said except that the US is able to stop it. Think about it: Wouldn't Israel simply use these same tools in the US to install a puppet president they can easily manipulate?
You are correct. Robustness requires a system that is working within it's tolerance margin, and stressing that inevitably leads to failure. A fault-tolerant system in this case would require a large amount of redundant humans. Unfortunately, the capitalist mindset prevents accepting any amount of "waste" as tolerable, which makes a robust system impossible to implement over time. Every system touched by a capitalist optimizer will eventually fail.
The idea that waste must be reduced is killing society, and this mindset must be addressed first before any other safety-critical system can be made reliable again.
I am alarmed at the high number of supposed engineers on this thread that are seemingly unaware of how safety-critical systems work. Literally every other piece of this system has redundancy built into it. Robustness is never optional in a scenario involving human safety.
A terminal still offers a more composable interface than a GUI. Analog feedback is still a concern for high level pilots. You are confusing power tools with entry-level instruments.
On the other hand, as long as the entire internet goes down when Cloudflare goes down, I'll be able to host everything there without ever getting flack from anyone.
You're ignoring the fact that going outside to protest wasn't something you could just decide not to do, just like buying groceries. BLM protests and gathering indoors for fun are not equal.