3 ms·

Sure it is. Don't the "DevOps" administer, provision, and manage your systems? Have you ever seen a unix guru who didn't have scripts and use automated tooling?

Sure it is. Don't the "DevOps" administer, provision, and manage your systems? Have you ever seen a unix guru who didn't have scripts and use automated tooling? And when a system fails (and they all fail eventually) the routine is the same no matter what you want to call it.

estefan 11y ago
At one company our "unix guru" didn't bother to set up anything like ganglia so when the server's disk got full and brought down the product he looked like an idiot... Maybe it's good vs bad but it happens. In the puppet/chef era I'd have said you needed to have a background in coding to be a good devop, but ansible has changed that now I think.
- PaulHoule 11y ago
  You haven't lived if you haven't filled a disk at some point.
  - BingsF 11y ago
    While true, this doesn't make for a good excuse to let your employer's server go down when its disk fills.
- partisan 11y ago
  Hindsight is 20/20. Plus, you learned from his mistake and now, anywhere you go, you can remind the unix gurus to prevent that type of thing from happening.
brianwawok 11y ago
There are two kinds of DevOps. You have DEVops... think of a web developer who also knows linux. Then you have devOPS... think of a sysadmin who knows bash and python. The former is where I think the value comes.. they find ways to automate your infrastructure and do lots of cool things. The later tend to make webs of bash scripts that you have to delete when they quit because no one understands them.
- dozzie 11y ago
  ...yet when you start looking at how this automated infrastructure works, it turns out to be sloppily crammed together however the webdev happened to work, be very brittle, failing every now and then, requiring constant attention and adjustment, non-standarized with tremendous ramp-up time for anybody who needs to take over, and with components mingled together without any separation, so it couldn't be replicated somewhere else. All that because the webdev was learning new Csharp.JS framework like dozen before, being too busy to learn how package system or daemonization or networking or RPC or SSH or push vs. pull architectures worked and what they are good at, or what tools and why a seasoned sysadmin uses for automation. What you really need is not a dilletante armed with sharp and pointy PHP-du-jour, but a system programmer. There used to be such a profession, the guys who wrote syslog, init, bash, grep, awk, libnss, and tons of other goods people today either use without much thinking or don't know existence of at all.
- rejschaap 11y ago
  You basically just argued there is no such thing as devops, just developers and system administrators.
  - reality_czech 11y ago
    Next thing you know, he's going to be telling you that your 360" review is actually a yearly review, that your scrum master is actually just a team lead, and that your gluten-free bread is actually just a rice cake with sugar. These old-timers sure do get some funny ideas.

estefan 11y ago

At one company our "unix guru" didn't bother to set up anything like ganglia so when the server's disk got full and brought down the product he looked like an idiot... Maybe it's good vs bad but it happens. In the puppet/chef era I'd have said you needed to have a background in coding to be a good devop, but ansible has changed that now I think.

PaulHoule 11y ago
You haven't lived if you haven't filled a disk at some point.
- BingsF 11y ago
  While true, this doesn't make for a good excuse to let your employer's server go down when its disk fills.
partisan 11y ago
Hindsight is 20/20. Plus, you learned from his mistake and now, anywhere you go, you can remind the unix gurus to prevent that type of thing from happening.

brianwawok 11y ago

There are two kinds of DevOps. You have DEVops... think of a web developer who also knows linux. Then you have devOPS... think of a sysadmin who knows bash and python. The former is where I think the value comes.. they find ways to automate your infrastructure and do lots of cool things. The later tend to make webs of bash scripts that you have to delete when they quit because no one understands them.

dozzie 11y ago
...yet when you start looking at how this automated infrastructure works, it turns out to be sloppily crammed together however the webdev happened to work, be very brittle, failing every now and then, requiring constant attention and adjustment, non-standarized with tremendous ramp-up time for anybody who needs to take over, and with components mingled together without any separation, so it couldn't be replicated somewhere else. All that because the webdev was learning new Csharp.JS framework like dozen before, being too busy to learn how package system or daemonization or networking or RPC or SSH or push vs. pull architectures worked and what they are good at, or what tools and why a seasoned sysadmin uses for automation. What you really need is not a dilletante armed with sharp and pointy PHP-du-jour, but a system programmer. There used to be such a profession, the guys who wrote syslog, init, bash, grep, awk, libnss, and tons of other goods people today either use without much thinking or don't know existence of at all.
rejschaap 11y ago
You basically just argued there is no such thing as devops, just developers and system administrators.
- reality_czech 11y ago
  Next thing you know, he's going to be telling you that your 360" review is actually a yearly review, that your scrum master is actually just a team lead, and that your gluten-free bread is actually just a rice cake with sugar. These old-timers sure do get some funny ideas.