It was being cheap, not woke, that got them killed. Step away from the culture wars and pay attention.

Well you're not, at 12 cores loaded you're thermally limited and tests show no difference to speak of at all. You get a slight boost to single threaded performance but overall this is the dullest upgrade in ages and creating a whole new XT line for it is silly. Should have just called it 3910X, 3810X and 3610X, at least then they'd get points for honesty.

Jurisdiction is not the only kind of power. China has repeatedly shown that they don't care if you're an American speaking out in America, if you're badmouthing China they will do what they can to make your life miserable. Of course they'll wrap their demands in weasel words and so will the corporate chain and your business partners but the real message is "STFU or we'll lose our business with China". Like any negotiations will be mysteriously stuck in a quagmire that'll equally mysteriously resolve itself once you're relieved of your position or the partnership is terminated.

To be honest Taiwan's problem is that the had delusions of grandeur, in 1971 when they lost their seat on the UN Security Council they themselves strongly refused any division of China and the creation of an independent Taiwan. Instead they forced it into a vote of who was the "legitimate" owner of China's seat and long story short they lost. If they wanted independence back then, they probably would have gotten it. Their problem now is that China has flipped the script on them, because they were pouting over the loss of the mainland China they never cut their losses and got their independence so now China wants them to answer to Beijing.

They don't realistically have much political or public support in Taiwan though. China is pressuring every other nation to recognize China's claim to Taiwan if they want to have relations with China, but that only makes it a hostile territory they could occupy at great cost - and probably not without an actual shooting war with an army supplied by the US military. My guess is they're eyeing the situation in Hong Kong waiting for the right moment to say status quo is no longer an option, it's either independence or submission and we choose independence. They must see that there's no future in trying to appease China.

Write no, compile yes. He's pulling code from all the subsystem maintainers (lieutenants) to create the master branch. And they again are mostly pulling other people's patches. They're supposed to make sure it's clean and tested before it reaches Linus but that's not always what happens. If it breaks or he finds bad code it goes back down the chain of command again so they can fix their code again and resubmit.

In rocket science I'd say 10+ launches is well into established already. The Falcon Heavy got their military certification after just three launches. The SLS is still planning to launch crew on their second flight. I suspect your sig is very relevant here:

My guess is one faulty part or installation brought the mission down. This was not a violent failure, the rocket just lost engine power and stopped. Which means it's probably the QA department and not the design department that needs to get to work.

Funny, I wish I had more of the first bit. Not my fuck-ups but the best times are those where I've been living in the moment and let go of all the rational, dull downers like that this junk food isn't good for me or that partying this hard will give me a hangover tomorrow or that this vacation is burning a hole in my wallet. Like I know that I'm overall fairly rational and got my shit in order, can't I get a break when I have a few excesses without that nagging party pooper in the back of my head. It's okay to have a plan for where you want to be five years from now but it's also important to accumulate happy memories on the way.

Bad employees also tend to think they're irreplaceable and they're as common as bad managers. The difference is that bad employees are the manager's problem, a bad manager is your problem. Unless you become the manager, then you see the other side of that equation. I don't mind taking on a tech lead position but if I went into middle management I'd probably end up strangling someone. I have the feeling I'd be one of those technically bright but horribly micromanaging bosses who'd rather be doing my underlings job than doing mine. Which would be mostly herding cats, running interference and communicating upwards, downwards and sideways in the hierarchy.

Intel drank that kool-aid and decided to make a CPU architecture where practically everything was exposed to the compiler, it's called IA-64 aka Itanium. They soon found out that a design grounded in reality beats ivory tower theory. ARM is also CISC with micro-ops these days, some instruction complexity is best left hidden. Forcing the compiler to deliver micro-instructions only hurts performance.

The reason I use whitelist and blacklist is that they're not the same as what's allowed/denied. If you implement say a spam filter and somebody wonders why something does or doesn't get through then "it's whitelisted" or "it's blacklisted" are complete explanations that someone has overridden the regular spam filter that'll also allow and deny emails. If the rules are exhaustive there's no reason not to be more direct. I have no strong opinion about master and slave, I tend to use manager/worker anyway since that's been the most relevant structure for me. But as long as people don't go crazy on the euphemisms we'll be fine. Rudolph/reindeer anyone?