What's impressive is that if you look at the issues PATCO struck over, it was basically identical to the problems ATC faces today. The problem being that everything has only gotten a lot worse for ATC controllers.
The union pretty loudly and early on pointed out major problems with that job and the response of ignoring them for 4 decades is what's driven us to the current situation.
A union that isn't allowed to legally strike when needed isn't a useful union though. The state that ATC has been in for the decades after that suggests to me that they were correct to strike.
Multiple economic write ups have concluded that Reagan’s “stick it to the upstart guy” cost us tax payers way more than it would if they’d just acceded and maybe even thrown in a gracious bonus to say thanks.
Larger sociology say the intangible cost to labor balance laws actually were much more.
Reagan’s trickle down (great euphemism for “piss on”) movement was the beginning of the demise of the GOP IMO. Disclaimed: I voted both times for him and many GOP followers.
and now the country of freedom is free to deal with ATC shortages that leave people managing two runaways and ground traffic by themselves in a a major airport
ah, truly a decision with no consequences
tl;dr just because it's a legally allowed decision, doesn't mean it's a right decision
There’s a pretty big difference between “economic leverage” when it means your stores might be shut down for a couple of weeks vs. all of the people moving, shipping, etc. in an entire country.
A strike being inconvenient? Workers leveraging how crucial they are? The stoppage of work having massive impacts across the country? Huh, maybe the powers that be should listen to the workers when they ask nicely for better conditions instead.
Isn't the "inconvenience" the entire point of a strike? A strike where nobody was affected in any way wouldn't be a very effective one, after all, so the larger of an inconvenience the more likely for the other side to relent to the unions demands.
Probably some fraction of the civilians blown up by Israeli terrorist phone strikes and bombing raids; there's a reason Hezbollah maintains some level of support in the region.
35-ish years ago there was a pitch for cheap, high velocity, spin-stabilized rockets that were deployed in dense pods on the A-10. The rocket's seeker could divert some small amount of thrust at an angle for guidance, but otherwise that was it. I can't recall if it ever made it out of the pilot phase, but obviously nothing new under the sun.
There are other mitigations though: You can pass expected owner accountId on S3 operations and you can create SCPs that restrict the ability of roles to write to buckets outside the account. Unless you have an account that does many cross-account S3 writes, the latter is a simple tool to prevent exfiltration. Well, simple assuming that you're already set up with an Organization and can manage SCPs.
Having worked in this space for years, it's not nearly as bad as you think. IaC tools can all look up the accountId/region for the current execution context and you can use SSM Parameters to give you a helpful alias in your code.
Also, if you have a bunch of accounts, it's far easier for troubleshooting that the accountId is in the name: "I can't access bucket 'foo'" vs. "I can't access bucket 'foo-12345678901'"
reply