Thanks for that context.

Or, more charitably: use the Strangler Fig method to modernize your systems, and start with low-hanging fruit.

Did you forget your WiFi password?

I agree that the US is wildly overpaying for what it gets, but from what I can tell we are directing that money to US-based factories. Just because those factories are also producing improved weaponry doesn’t mean they can’t produce more basic ammo, albeit at lower volume. We don’t need full-scale production capacity when we’re not in a large-scale war.

My point is more that we're not building factory capacity for the sorts of sustained output a large war would require.

Whether true or not, the article’s author also argued this point in 2023 (link below), and this article uses some of the same language (empty bins) as the paper.

https://www.csis.org/analysis/empty-bins-wartime-environment...

For me, the main point comes down to exactly how much of a weapons stockpile should a peaceful nation carry? We (US) already have a large number of nuclear weapons, and have been fighting a proxy war of sorts with Russia for over a year. Now we’re the aggressor in several other high profile strikes that have taken out the leaders of several nations. In my opinion, this _should_ be stressing the supplies of our military, _because it’s not (or shouldn’t be) our normal mode of operation_. We already have mechanisms like the Defense Production Act which would allow us to rapidly scale the creation of weapons when needed. Carrying enough weaponry to fight an extended large-scale conflict is incredibly wasteful, and seems like it would mostly serve those who would profit from the required spending to accomplish it.

Is humblebragcomplain a word? ;)

I like to call it "suffering from success" from the meme

https://knowyourmeme.com/memes/subcultures/suffering-from-su...

I think a better policy would be to disallow bucket names that follow the account regional namespace convention, but don’t match the account id indicated in the name.

So no bucket sharing across accounts?

Limiting the creation of buckets that use the account namespace conventions doesn't affect whether other accounts can access it.

If a sleep-deprived senior shouldn’t have access to prod, I think we have big problems, frankly.

Which, if you're Google-sized, you have follow-the-sun rotations, in order to avoid that problem. But what about the rest of the class?

But putting all of them in a tidy list definitely changes the value.

There are definitely problems with homebrew, but user-owned directories isn’t high on the list, imo. Your ssh private keys, startup scripts, and any number of other things that can do serious damage are all owned by your user. Frankly, if install vim as my user, I want it to execute instead of the built-in version, unless I’m running a command with sudo, in which case the system binaries take precedence. So I don’t even see path order as a major issue here. If someone has compromised your user, you’re compromised whether you’ve used homebrew or not.