DevOps didn’t exist when I started as a developer
1–10 of 176 posts
Re: DevOps didn’t exist when I started as a developer
#2Generally Ive found tight feedback loops to be incredibly productive. Whether its for product, release, design, development. Having the ability to make modifications with feedback from customers, systems, business partners and colleagues changes everything.
Re: DevOps didn’t exist when I started as a developer
#3Nailed it.
I also got a chance to work in such an organization in the 00's, where dev and ops closely aligned with each other's work to produce truly reliable, repeatable, fast, quality products, often. It was fantastic. Nobody would say "oh but you can't do that, that's not Infrastructure as Code!" They would say, "what can we all do to make this better?"
Re: DevOps didn’t exist when I started as a developer
#4I found this line interesting, everything else considered:
DevOps is NOT…easily achieved nor implemented
Debatable, at least IMO. DevOps isn't easily achieved nor implemented if you're trying to implement ALL THE THINGS to say you did and check-off a series of "We did DevOps thing x" boxes as so many companies appear to want-at least from reading various DevOps-y job descriptions lately.
It is easier implemented if, like Gene Kim tells us in "The DevOps Handbook"-we start our DevOps transformations with a small, sympathetic team and iterate outward.
Re: DevOps didn’t exist when I started as a developer
#5Generally Ive found tight feedback loops to be incredibly productive. Whether its for product, release, design, development. Having the ability to make modifications with feedback from customers, systems, business partners and colleagues changes everything.
Yeah, the faster you’re able to iterate, the faster you can improve.
Re: DevOps didn’t exist when I started as a developer
#6Nailed it. I also got a chance to work in such an organization in the 00's, where dev and ops closely aligned with each other's work to produce truly reliable, repeatable, fast, quality products, often. It was fantastic. Nobody would say "oh but you can't do that, that's not Infrastructure as Code!" They would say, "what can we all do to make this better?"
Isn't it amazing that working on/as a team is seen as an outlier?
We need more of this.
Re: DevOps didn’t exist when I started as a developer
#7Sidebar: does anyone else get the feeling that infrastructure as code is just cloud vendor lock-in by another name? Especially since the output of the code ends up being wild unstructured JSON/YAML files with no spec or discernible schema.
My favorite is how in the Microsoft toolchain you can build a CI pipeline in a visual UI on the right that automatically updates the YAML file on the left. “We know you don’t want YAML, but we also know your boss says you need infra-as-code...”
Re: DevOps didn’t exist when I started as a developer
#8What bunk.
In the real world "DevOps" simply means "sysadmin that can write scripts".
Re: DevOps didn’t exist when I started as a developer
#9Lots of things people think of as crucial today didn't exist when I started. And the overall ratio of successful work to unsuccessful work was just as high then as it is now.
Re: DevOps didn’t exist when I started as a developer
#10Generally Ive found tight feedback loops to be incredibly productive. Whether its for product, release, design, development. Having the ability to make modifications with feedback from customers, systems, business partners and colleagues changes everything.
Yeah, the faster you’re able to iterate, the faster you can improve.
Only if you make meaningful iterations. I see a lot of demand for iteration coming from above and suddenly you are in this cycle of fixed length “sprints” where you worry more about releasing on time instead of meaningful releases.