It’s a Journey – Come along for the ride.

All journeys have 2 beginnings.

There’s the first step of the journey, and then there are all the things that came before the journey.

For the DevOps community, this journey started somewhere after 1843 when Ada Lovelace wrote the first computer program.

All people have points of view, my point of view is that “DevOps” (at least in the HR world) has become “The cool word for systems administrator”.

For many network ops people and system administrators, their view is that “DevOps is already All-about-programming, so what’s your point?

That’s a pretty wide gap. It’s a gap that I may or may not try to bridge. Either way, not calling out the gap would be wrong.

The point of “The Dev In DevOps” is to give a place for those who want to see the bigger picture to hang out.

For the developers who have an interest in: home lab, their A+ cert, picking up a new language, building their CI/CD pipeline, tuning their code, effortless refactoring, reducing code duplication, building “self-aware” code that fixes itself while sending actionable alarms to the 24/7 people that never get a break.
This is a place for you.

For the business person who has noticed that their coding projects have an amazing velocity of new features over the first 6 – 18 months, but sometime over the first 2 years, the ability to make changes “approaches zero”. It just seems to be harder and harder to get a new feature in.
This is a place for you.

For anyone who has watched project start out with about 18 deployments per year (every 2 weeks for 9 months out of the year), but maybe the project was constantly having high incidents, and the customers were complaining.
Maybe for you, someone suggest that “we eliminate the meaningless churn”, and reduce our schedule to 3 quarterly deployments per year, with hotfixes “as needed.” Maybe now, changes that took 2 weeks to develop prior to go-live, now take 2 quarters.
This place is for you.

If any of the above experiences resonates with you, then you’re invited to come in, pull up a seat, limber up some of your best “lessons laced” war stories and get comfortable.

The DevInDevOps may or may not have the answers you’re seeking, but hopefully with all of us discussing the issues, together we can find some solutions that will help some of us.
(Because we’ve all experienced the chaos that is 99% of of “one size fits all” solutions.)