Earlier quoted context omitted.
Yes, that's kind of interesting, isn't it? If those horror stories are true (and we have no reason to doubt they are), it kinda shows that the way you treat your employees doesn't really matter to your success. It certainly matters a lot to them; it matters from a moral point of view; but from a practical point of view the only individuals whose happiness matters are the customers. Of course, if your employees are so…
On the contrary, the way Amazon treats their employees does harm them substantially, they just haven't paid the price visibly to the public (or quite as hard as they will, eventually). Attrition at Amazon is at horrific rates. I know the actual number, though I'm pretty sure that'd violate my NDA to reveal. It's high. It's really high. Guess a really truly terrible number. It's probably higher than that. The stream o…
If it hasn't hit them yet, it might after the rant.
Given the Dilbert Employer From Hell publicity generated by the rant and the subsequent discussion, I'd say that they might have trouble filling in for the people that leave. Heck, even some of their current employees might read the rant and realize how crappy their current situation is.
Off on a tangent:
"I couldn't even run multiple dev environments on it, like I had to for my JOB, and building my code took 12 full minutes, instead of, say, 3."
Local dev environments? My current workstation has a mere 2GB memory and an Athlon X2 which was all the rage in 2005 :) The builds fly, because they are delegated to a compile farm. The added benefit is that I don't have to muck with the build tools settings.