Premature abstraction is one of the worst pitfalls when writing software. It's paid for up front, it costs developer time to understand and work with, it adds complexity (tech debt), increases likeliness of bugs, and increases refactor time. All for someone to say "if we ever want to do X". If we wanted to do it, we'd do it now.
I truly believe this comes from devs who want to feel smart by "architecting" solutions to future problems before those problems have become well defined.
Not who you're responding to, but I'm not a huge fan of vibe coding for 2 reasons: I don't want to use crappy software, and I don't want to inherit crappy software.
Your second example of a choice is a consequence of a choice. Those companies chose not to comply with new reporting rules which resulted in having their Pentagon access revoked. This is an important distinction when given "choices" that aren't really choices but mandates.
As far as how this YouTube scenario is different, people can host their content elsewhere, but there's only one Pentagon in the US.
Unknowingly, I've trained my friends and family to assume they aren't going to get an answer immediately. They now text to call when I have time. Or they immediately get to the point: "wanna go riding tomorrow" instead of "hey whats up". Some people are put off by this and others find it endearing, I couldn't care less what they think. My time is my time and I do with it what I please. That means being there for others when they need it, which means being the hell off my phone when I am there.