It's tempting to put all the sysadmins in one group, all the dba's in one group, all the front end guys, etc.

It's tempting to put all the sysadmins in one group, all the dba's in one group, all the front end guys, etc. There is some value to that. But if you think about when stuff really happens, you sort of need all those people working on one project. It's tempting to say, oh there's not enough work for a sysadmin full time. Really? do you have solutions for backups, logging, monitoring, and upgrades? does it all really work? I don't mean to harp on sysadmins, programmers don't test, managers coast through meetings. Amazon's everything is a service seems like a nice way to be somewhat resilient against that kinda stuff. I think when stuff is broken out the other way, by function rather than project, managers want to protect their resources. Use as few resources to complete the narrow task, rather than doing what really needs to happen to be successful. (like actually handling failure modes) Big organizations have the evaporation problem too. A system can be really dysfunctional, but it's fine as long as it makes money. When competition heats up, the smart people just go find other jobs. So, the second best and second brightest take charge. They solve problems as well as they can, but often it's stuff like stopping reimbursement for cell phones. It's hard. There's a season for everything. Organizations grow and thrive, get sick, recover, change shape, all sorts of crazy things.

Posted by jfoutz on Jun 13, 2015, 7:17 PM

Tags

• pricing (Other)

Related issues

• Not at all, actually.
• A car battery with reduced range is still perfectly useable as a storage battery for a PV system.
• Here in Argentina we are in permanent summer time GMT-3 since a long time, but we should be in GMT-4.
• You should do some basic research yourself.
• Well, actually not.
• I have a 2022 mini that I use constantly.