As a sysadmin these kinds of articles have a sort of duality to them.
On the one hand they're insulting. The author is clearly wholesale ignorant of the vast majority of sysadmin roles and responsibilities (and why companies need them) and yet feels like they know what they're talking about enough to declare the role dead.
On the other hand, developers with no clue whats entailed in sysadminning are the number one source of our job security, so its a backhandedly good thing.
Please, by all means host your startup's database in a "aaS" solution with ~500 IOPS (except sometimes! at random!) across a 50 - 100ms link. It will make me look like a wizard when I clean up your rookie moves.
I spent two days trying to figure out how to compile a 32 bit library on a 64 bit system.
A sysadmin would have figured it out in 5 minutes, and lazily dropped by my desk to show me where I went wrong.
In my experience, sysadmins aren't just people who keep things running during the course of Business As Usual, you guys are also a terrifying repository of arcane knowledge.
On the one hand they're insulting. The author is clearly wholesale ignorant of the vast majority of sysadmin roles and responsibilities (and why companies need them) and yet feels like they know what they're talking about enough to declare the role dead.
On the other hand, developers with no clue whats entailed in sysadminning are the number one source of our job security, so its a backhandedly good thing.
Please, by all means host your startup's database in a "aaS" solution with ~500 IOPS (except sometimes! at random!) across a 50 - 100ms link. It will make me look like a wizard when I clean up your rookie moves.