News for hackers. Stuff that matters.
Re:Notes on Google's Site Reliability Engineering Book by peterwwillis on Thursday April 14, 2016 @09:48AM (#11496609)
Well that's just the thing - an organization that has a "system" or "process" for handling employees and their work is by design less than flexible. In a small to medium sized business, you might have 3 completely separate roles, and others might pitch in as needed. But at a large corporation, it's simpler and more efficient for them to have one person who does one job. When the peg no longer matches the hole, they are replaced or reassigned. Which is sad, because people with valuable skills are often underutilized. I feel like companies like Valve might have the right idea going forward.
Re:Notes on Google's Site Reliability Engineering Book by btilly on Thursday April 14, 2016 @01:14PM (#11498566)
The problem is that larger organizations actually need to have a defined process of some sort. There is a point beyond which individual judgment doesn't scale.

In general I believe that Google has a pretty good process. However every process has bugs. And I happen to have encountered one where they pick people who are qualified in one role into a more experimental one, and it only sometimes works out for them.