The sheer scale of a trillion dollars can be hard to comprehend. Let me put it in perspective. You would be able to buy 42 miles of high speed rail in California with that much money.
My house burned down. I lost everything. I can’t rebuild. As a 42 year old man with 2 kids, I’ve had to move into my parents’ house, and I’m getting attacked for that? This is journalism? This is why no decent people ever get into politics. This is why you only have goblins running everything. God help you if you try to make things right for your community…if you lose your entire town, “journalists” mock you for not making your kids sleep in the toxic dirt on your burned out lot. Who raised you, dude?
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
idk at this point there are 2 options:
either they don’t know what squash and merge button is doing
or producing a complete slop, cause no one can review and validate 20 commits every hour 13 hours in a row even for a simple functional correctness
when deciding company culture a tempting option is be "elite" or that you're doing incredibly important work
this almost always backfires because you end up with regular people who think they're super special just for being there
and the culture becomes one of delusion