Nobody is going to attack us unless we go out into the world creating enemies.
724 karma · joined July 24, 2025
Nobody is going to attack us unless we go out into the world creating enemies.
Waymo is replacing human drivers with a capital-intensive fleet business, a substantially more expensive vehicle, and still a large number of remote assistance staff, fleet operators, safety engineers, incident response, operations staff, etc.
But I'm not saying they can't beat a human driver, I'm just saying it hasn't been proven that they will. It may only be that the highest demand markets will provide a sufficient enough utilization to make it economically viable.
Or really, it's not disguised at all. The company is named after Tolkein's palantíri, so they weren't being shy about it.
It's a company that exists solely to exploit a loophole that shouldn't have been upheld, effectively eliminating the fourth amendment.
The benefits for them include:
- replacing workers with lower quality (but good enough) AI solutions, which degrade the quality of nearly every product or service for the consumer, but not by enough to offset the labor cost savings
- mass surveillance at low cost, a way to take the absurd amounts of data humanity now produces, and use to subjugate them
- propaganda/deception/misinformation, a new vector for propaganda which people are naively inclined to trust. bonus points for the "flooding the zone" strategy which AI makes easier
Benefits to the worker:
- lower cost of goods and services (but not for you, silly - they'll still be taxing you via inflation to fund their wars of conquest)
- you won't have to work anymore
- you won't have to eat anymore
I'm afraid it's far too late.
- You rarely write loops at work
- Every performance issue is either too many trips to the database or to some server
- You can write O(n^n) functions and nobody will ever notice
- The hardest technical problem anyone can remember was an N+1 query and it stuck around for like a year before enough people complained and you added an index
- You don't really ever have to make difficult engineering decisions, but if you do, you can make the wrong one most of the time and it'll be fine
- Nobody in the shop could explain: lock convoying, GC pauses, noisy neighbors, cache eviction cascades, one hot shard, correlating traces with scheduler behavior, connection pool saturation, thread starvation, backpressure propagation across multiple services, etc
I spent a few years in shops like this, if this is you, you must fight the urge to get comfortable because the vibe coders are coming for you.
If a task before would take you ten hours to think through the thing, translate that into an implementation approach, implement it, and test it, and at the end of the ten hours you're 100% there and you've got a good implementation which you understand and can explain to colleagues in detail later if needed. Your code was written by a human expert with intention, and you reviewed it as you wrote it and as you planned the work out.
With an LLM, you spend the same amount of time figuring out what you're going to do, plus more time writing detailed prompts and making the requisite files and context available for the LLM, then you press a button and tada, five minutes later you have a whole bunch of code. And it sorta seems to work. This gives you a big burst of dopamine due to the randomness of the result. So now, with your dopamine levels high and your work seemingly basically done, your brain registers that work as having been done in those five minutes.
But you now (if you're doing work people are willing to pay you for), you probably have to actually verify that it didn't break things or cause huge security holes, and clean up the redundant code and other exceedingly verbose garbage it generated. This is not the same process as verifying your own code. First, LLM output is meant to look as correct as possible, and it will do some REALLY incorrect things that no sane person would do that are not easy to spot in the same way you'd spot them if it were human-written. You also don't really know what all of this shit is - it almost always has a ton of redundant code, or just exceedingly verbose nonsense that ends up being technical debt and more tokens in the context for the next session. So now you have to carefully review it. You have to test things you wouldn't have had to test, with much more care, and you have to look for things that are hard to spot, like redundant code or regressions with other features it shouldn't have touched. And you have to actually make sure it did what you told it to, because sometimes it says it did, and it just didn't. This is a whole process. You're far from done here, and this (to me at least) can only be done by a professional. It's not hard - it's tedious and boring, but it does require your learned expertise.
Iran (1953) - overthrow of the Shah by the CIA
Guatemala (1954) - overthrow of an elected government on behalf of US corporate interests
Cuba (1961) - invaded Cuba via proxy forces, attempted to assassinate Castro (Bay of Pigs)
Vietnam, Laos, Cambodia (1955–1975)
Chile (1973) – overthrow of Salvador Allende
Nicaragua (1980s) - overthrow the Sandinista government (Contra war) without international authorization
Panama (1989) - invaded and overthrew the government without international without international authorizationauthorization
Iraq (2003) - invaded and overthrew the government without international authorization
Serbia (1999) - airstrikes without international authorization
Libya (2011) - exceeded authorization by UN to effect regime change
Syria (2014–present) - US military occupation and oil seizure is ongoing
There are many more, these are the more notable ones
LLMs can use linters and type checkers, but getting past them often times leads it down a path of mayhem and destruction, doing pretty dumb things to get them to pass.