Live data from Hacker News

DevOps didn’t exist when I started as a developer

circleci.com

171–176 of 176 posts

Re: DevOps didn’t exist when I started as a developer

#171

Earlier quoted context omitted.

The article is lost on me too. ~15 years professional experience as a software developer and I never had to deal with an "Operations" team. My understanding is that it's the people that would be doing Amazon's job if you were trying to not use AWS or some other cloud service? "Devops" means not fighting with those people??? haha

I take it you’ve never worked in any of the Fortune 500, then.

I've worked for a Fortune 500 company for the past 5 years, still nope.

Re: DevOps didn’t exist when I started as a developer

#172

Earlier quoted context omitted.

I take it you’ve never worked in any of the Fortune 500, then.

I've worked for a Fortune 500 company for the past 5 years, still nope.

You configure the Cisco routers, then?

The company doubtlessly has a CEO, too, even if you are so compartmentalized as to never speak with her.

Re: DevOps didn’t exist when I started as a developer

#173

Earlier quoted context omitted.

I take it you’ve never worked in any of the Fortune 500, then.

I work for a Fortune 150, but I’ve never worked with a operations, devops, etc. team.

Who monitors production? Who provisions routers, wireless access points, VPN servers?

Just because you are “throwing it over a wall” doesn’t mean the team on the other side doesn’t exist.

Re: DevOps didn’t exist when I started as a developer

#174

Earlier quoted context omitted.

I've worked for a Fortune 500 company for the past 5 years, still nope.

You configure the Cisco routers, then? The company doubtlessly has a CEO, too, even if you are so compartmentalized as to never speak with her.

I think the mismatch is that I never developed websites, think games, media tools, developer tools. Anytime there was a dependency on a web component I was using a cloud service, external or internal. Internal cloud services were operated by different BU's like a separate business. Software was distributed via boxed CD or 3rd party web stores. I've never looked into the eyes of someone that configures routers or even heard them mentioned in all my years. They were always essentially in a different company.

Re: DevOps didn’t exist when I started as a developer

#175

Earlier quoted context omitted.

You configure the Cisco routers, then? The company doubtlessly has a CEO, too, even if you are so compartmentalized as to never speak with her.

I think the mismatch is that I never developed websites, think games, media tools, developer tools. Anytime there was a dependency on a web component I was using a cloud service, external or internal. Internal cloud services were operated by different BU's like a separate business. Software was distributed via boxed CD or 3rd party web stores. I've never looked into the eyes of someone that configures routers or even…

That makes sense. It is modern in the sense of being structured as cloud services, yet the proverbial walls between Dev and Ops were tall and sturdy, as is the tradition.

Re: DevOps didn’t exist when I started as a developer

#176

Earlier quoted context omitted.

> Personally I think DevOps is like religion As long as no-one is knocking on my door asking if I have five minutes to discuss Agile development methodologies. I could reasonably defend most of what people attach to the "DevOps" buzzword as sane practices most of us were already doing before the hoopla. Agile (with a capital A) is the absolute worst thing that has ever happened to the software industry. Kill off that…

The "Agile" most people complain about is the same thing we had before "Agile" came. You've got 2 broad camps: people who really want to do adhoc development and would like an industry accepted word to call doing whatever-the-heck-I-feel-like. The other side are the people who, having risen to a position of influence are desperately trying to add value, even though they don't actually do anything that results in code…

It’s not really common sense, and the agile I know of says quite a lot about how to accomplish goals, if your goal is “delivering quality software products/services”.

There also is bullshit Agile of course, which you describe well, but that’s no different from any old software process that’s more bureaucracy than content.

My point is that the cynicism ignores actual differences in practice and process that can have an order of magnitude impact on performance, and its not always “obvious” for smart people to adopt such practices.

Consider Lean manufacturing: the Japanese thought it was just a common sense extrapolation of Henry Ford’s system of organization. It still took decades for the US auto manufacturers (including Ford!) to wrap their heads around it.

There were plenty of crooks and charlatans in that field too. It didn’t negate the importance of what Toyota had figured out.

Post reply on HN