Last beer though...
"First Piece" folks should get more flak as they've destroyed a baked work of art.
https://en.wikipedia.org/wiki/Simulation_heuristic
AFAIU, when something bad happens to us, we focus our regret on the smallest/nearest action that could have been undone to change the outcome. So in this case, the bad thing being that you wanted a piece and there are none left--it's natural to blame whomever ate the last piece, because it's easier to imagine an alternate reality where the last piece wasn't eaten, than an alternate reality with some earlier piece not being eaten and everybody subsequently encountering a cake with one additional piece.
However, these immediate policy violations are strange to me. As someone who writes software for a lot of field crews, these kinds of exceptions happen _all the time_ and very often they're for explainable reasons. (the guy's hands were busy, he asked his buddy to move the heavy tool).
I'm sure they're aware of this but you have to work in some kind of tolerance to these kinds of compliance violations, because the ultimate goal is increased safety, not finger-wagging.
Eg. If an employee has a workplace accident, company distances itself / minimizes cost by citing all your workplace safety violations that were conveniently recorded.
More optimistic use would be for re-training, identifying superstar employees. But saving on lawsuit costs is the big dollar win and probably the motivating factor (In my cynical opinion)
http://www.zdnet.com/article/why-windows-must-die-for-the-th...
Was a pretty interesting read today.
WinRT/UWP is a toy application framework able to produce no better than toy apps. That is why any Windows application worth using is not "modern". The real story is that today's Microsoft can no longer execute and create something new on the same quality level as Win32 was in the 90s.
Sandboxing has nothing to do with it. You can sandbox win32 and in fact they do when you submit a legacy desktop app to the store.