2,714 karma · joined October 3, 2018
> According to a 2005 study, "Despite almost a century of scholarly debate on this question... there is still no consensus about whether and under what conditions Michels’s claim holds true"
Seems to contradict sections 5.2 and 5.5 in spirit...
Also, I read through that RFC several times and didn't find where it allows replacing 'Z' with space. Can anyone else find it?
It's interesting that the author mentions this, but doesn't make a connection between feeling burned out and feeling that they have to be personally responsible for everything the company does.
I don't even disagree with many of the demands of internal "activist", but the strategies they use (walkouts, trying to keep everyone outraged as much as possible) seem ineffectual to me: The main effect seems to be that it makes ordinary employees feel more burned out since they're made aware of many things that they're suppose to be angry about but at the same time they're powerless to change them. That's a recipe for burnout.
I get that the thinking is that ordinary employees are not powerless due to collective action, but for that to work you have to be a lot better at picking your battles. You can affect one to two larger things per year, so getting up in arms over every (comparatively) little thing just has the effect that your activism achieves nothing but burn out the people who want to have on your side.
It's way shorter, somewhat easier, more straightforward, and more expensive than Hollow Knight. Depending on how much time you have, all but the last of these can be pros.
My 2-year-old Intel MBP has 64 GB, and 8 GB of additional memory on the GPU. True, on the M1 Max you don't have to copy back and forth between CPU and GPU thanks to integrated memory, but the new MBP still has less total memory than my 2-year-old Intel MBP.
And it seems they just barely managed to get to 64 GiB. The whole processor chip is surrounded by memory chips. That's in part why I'm curious to see how they'll scale this. One idea would be to just have several M1 Max SoCs on a board, but that's going to be interesting to program. And getting to 1 TB of memory seems infeasible too.
Most of the additional chip area went into more GPUs and special-purpose video codec hardware. It's "just" two more cores than the vanilla M1, and some of the efficiency cores on the M1 became performance cores. So CPU-bound things like compiling code will be "only" 20-50% faster than on the M1 MacBook. The big wins are for GPU-heavy and codec-heavy workloads.
That makes sense since that's where most users will need their performance. I'm still a bit sad that the era of "general purpose computing" where CPU can do all workloads is coming to an end.
Nevertheless, impressive chips, I'm very curious where they'll take it for the Mac Pro, and (hopefully) the iMac Pro.
If you're just skimming, be sure to slow down and read the "Bodge Time" section.
In the English and Spanish versions, it was invented by Tony Hiam in 1980 in Seattle.
100 mil isn't peanuts, not even for Google.
The way you do this is interview elsewhere, get an offer for 40% more, and _then_ tell your manager that you have an offer for 40% more and that you'd really like to stay but they'd really have to do something about compensation. You'll get more than 5% then (but likely less than 40%). It's annoying that you have to invest the time for this, but it does provide data to your current company that your market rate is in fact what you think it is.