My former employer suffered more than one very serious work-stoppage (lost scores of manhours) over the whole LAN due to problems caused by a developer whose Windows Domain account (and primary login on the local PC) has Administrator rights on the Domain and (thus) on the local machine. (This is due to Devs *not* being experts in networking, security, application and service mgmt, windows domain policies, etc. If they were, they would not have needed a Windows SA, right?) It was only after this fiasco that the mgmt folks acceded to my plan.
It was a lot of work to set up, and a lot of pain the first couple of weeks to train/handhold the Devs, but it started to really work. Oh, it should be mentioned we has somewhat unusually high security requirements due to being in the financial sector and handling customer credit/debit card data, etc. But, really, most of this was designed and implemented to actually improve work processes and uptime. And it did.
While I totally appreciate what it's like to have to expend some adrenaline to stop when I was not planning to, I think we all know that any accidents caused by Car A stopping and Car B hitting car Car A in the rear are completely the fault of the driver of Car B, in cases such as we are discussing.
If you are a) following at a safe distance and b) paying attention to the car in front of you, there's no reason to get into an accident. But most people follow too closely and or are doing other things with their attention, like daydreaming, texting, yelling at the brats in back, etc.
Whether or not that guy in Car A is overreacting and slamming on his brakes when he really does not need to is irrelevent to a conversation about the cause of such an accident. The guy in Car B screwed up.
But, our is a culture that wants to blame everyone else for what we create. *shrug*
"Everything should be made as simple as possible, but not simpler." -- Albert Einstein