If the damage was large, it would be hard to cover up. And if it was very large the US would seek to minimize it. “A few people killed” might be interpreted as “probably a ton of people killed” by the enemy and they keep doing it. Zero information means you can’t argue the case one way or the other, and in those cases the project gets scrapped.
One of the most interest facts about this disaster is that if the submarine was standing on its tail straight up, its nose would be sticking 150ft OUT of the water it sunk in.
I also get the impression this is way more complicated than it needs to be. Or maybe it's simple and they keep inventing new terminology for stuff that basically already exists. The crypto bros did the same shit. Like, bidirectional communication has been a thing for decades. We're just changing what we call the client and the server? And the protocol is just strings the bot on the other end is a little better at reading?
Almost no one actually knows how to set up their monitoring. Like, they know the words but not the full picture or how the pieces should actually fit together. Then they do shit like this to try and make up for that fact.
I agree with you that Afghanistan is a much different country. My fear is that once the entire centralized theocracy is bombed out of existence it will open the door for localize warlords to begin carving up territory. The alternative is a Khamenei 2.0 character stepping in. But then the question is, will Israel/the US not just assassinate them too? I don't know but there's no way this ends well.
I have 100% failed interviews by giving that answer when their definition of scale was 10,000!!!! req/sec. Like sorry dude in 2026 that's not much different than 10 req/sec and my original design would work just fine... But that's what happens when your interviewer is a "senior" 24 year old just reading off the prompt.
The answer to this is almost always "NO" in my experience, because no one ever actually has good suggestions when it comes up. It's never "should we choose a scalable compute/database platform?" It's always "should we build a complex abstraction layer in case we want to use multiple blob storage systems that will only contain the lowest common denominator of features of both AND require constant maintenance AND have weird bugs and performance issues because I think I'm smarter than AWS/Google AND ALSO we have no plans to actually DO that?"
Iran is on “death ground” as Sarah Paine would say. It’s a TERRIBLE idea to put your enemy on death ground because all they can do is fight now. We’re going to keep bombing them until there’s nothing left. Iran is going to end up looking like Afghanistan (a broken country of small feudal states) at the end of this.
Edit: By Iran, I'm referring to what's left of the current Iranian administration and military, not the entirety of the Iranian people.
It often feels like Apple hires the best hardware and marketing people in the world and holds them to the highest standards, but the software design and engineering people are left to just kind of screw around, redesign stuff for shits and giggles, and laugh as people fill their forums with bug reports and (very obvious) feature requests.