In the realm of modern software, the discourse surrounding development methodologies is ceaselessly evolving. Below we're going to have a look at an insightful article by Richard Seroter, titled "The Modernisation Imperative: Shifting left is for suckers. Shift down instead", and how it adds an intriguing dimension to the concept of "shifting left" because of the unrealistic burden now being applied to developers. Mesoform will be looking at this to highlight valuable insights that can potentially reshape and refine our approach to software development practices.

Wondering how DevOps can transform software development? Discover expert solutions to streamline processes and optimise collaboration.

This episode's musings are about the negative effects of the positive attributes of generative AI

This blog is on the importance of NGINX and will discuss how Mesoform implemented it despite facing challenges. Making use of multiple technologies to secure your IT.

This blog is on the importance of automated compliance enforcement and will discuss how Mesoform implemented it despite facing challenges. Making use of multiple technologies to secure your IT.

Please feel free to download this page as a pdf

This blog is on the importance of having a centralised SIEM and will discuss how Mesoform created it despite facing challenges. Making use of multiple technologies to secure your IT.

Please feel free to download this page as a pdf

This episode's musings are about security-in-depth with a daft analogy of Google Cloud's VPC Service Controls. Making use of multiple technologies to secure your IT.

This episode's thoughts are around project to product transformation - a white paper by Ross Clanton and Amy Walters:

What we mean by "operations," has changed over the years and some ambiguity has resulted from the pace of change. I'd like to discuss some of these changes.

Firstly, let me explain why I believe I know a little on the subject. I want to invite you to come back in time to the Technology Management Centre for a large Telco in the early 00s where a young man has just sat down for his first day on the job and his supervisor, Spencer hands him a drive bay (hot desking was serious business here) and says, "I recommend you do a stage 1 install of Gentoo because it'll will be a good learning exercise to set up the Operaing System from scratch. Then, when you're done, we'll go over this script I'm working on to automate some tests on our new Cisco 10K routers."

I'd never compiled an operating system before that point, so we never made it to the script but it was the first time in my career when I was suddenly plunged into a world of highly skilled engineers and architects, simply doing some amazing things under very tight requirements and needing to be "DevOps", just to ensure their success. Scripting and automating tests, building our own configuration management system, measuring everything that moved, working cross-functionally, high collaboration and information sharing across teams were all just the norm. We'd also virtualised our environments and were even running containers in production over ten years ago.

From that point, my work career continued in much the same way. Sure, there has been some challenges trying to help some people see the vision but now there is a DevOps community and a wealth of literature, those challenges mostly went away and the approach was less about pushing an agenda to simply agreeing with peoples ideas as they embraced the philosophies as well.

Where did it all start

Some Context

Managing value-driven, cross-functional (ValCro) projects in JIRA can be challenging to keep everything cleanly wrapped up together. Here's a proven idea which may work for you too.

So going back a few years, I was working at a software company where IT Operations was in the common situation of constantly playing catchup with Agile software development. We were already hammering home DevOps processes like tight feeback loops, sharing, learning and automation but collaboration was still a problem. Mostly around communicating around interdependant work, forward planning any work dependencies and keeping semi-automated, low-effort reports across teams.