Re:The sad state of sysadmin in the age of containers
by redblacktree on Wednesday April 22, 2015 @09:57AM
(#9420412)
I think the reason this happens less and less is that sysadmins are cost centers, not revenue generators. When you have developers do that work (poorly or not), you don't have a group that's purely cost. Those costs get hidden in the development group.
Re:The sad state of sysadmin in the age of containers
by stephenr on Wednesday April 22, 2015 @10:12AM
(#9420521)
Whoops replied to wrong comment!
However yes the issue of a team that "doesn't make money" is very real. Maybe you it should be "marketed" like legal or accounting: it doesn't make money, it saves money caused by SNAFUBAR situations.
Re:The sad state of sysadmin in the age of containers
by acveilleux on Wednesday April 22, 2015 @11:26AM
(#9421100)
Indeed, the costs merely get hidden and a lot of system decisions boil down to one of:
1. I saw it done that way in some blog.
2. We did it like that at my last job.
3. Seems like it works.
Re:The sad state of sysadmin in the age of containers
by sshconnection on Wednesday April 22, 2015 @11:34AM
(#9421159)
That high school kid needs to install a web server. Is he going to hire someone? No. He's going to copy a curl command.
You wouldn't hire some high school kid who's just about taught themselves HTML by reading a book for a week, and get them to write your web application from ground up. You'd hire someone who knows what they're doing. Why is it seen as any different for Operations work? There is a reason systems administration is a skilled field, and a reason they're paid on a par with developers.