Infrastructure as Code: A quick and simple explanation.

And why ALL infrastructure should be in code

One of the most essential topics when you’re a Cloud Native Software Engineer is a concept called Infrastructure as Code. Yesterday as I started writing the second part to the series on monolith to Microservice series I realised I couldn’t start the post until I had addressed the essential topic of Infrastructure As Code.

Just like many concepts in technology, infrastructure as code sounds scary. But in reality it’s a simple concept that any software engineer (or would be software engineer) can easily understand. I promise. Once you get over the first few hurdles you’ll wonder why you didn’t explore it sooner.

By the end of this article you will understand what Infrastructure as Code is, why you need it and why you should ALWAYS create infrastructure in code and not manually. 

What is a Cloud Native Software Engineer?

And what it means for a Software Engineers Career.

Knowing just the basics of Software Engineering isn’t enough to thrive in today’s market. Many Software Engineers need to have drastically more knowledge of cloud platforms than they currently do.

Why? That’s today’s question. We’re going to be discussing what a Cloud Native Software Engineer is, why they exist, what their skills are and ultimately what that means for you as a Software Engineer.

By the end of this article you should know exactly what a Cloud Native Software Engineer is and why that matters for your career in Software Engineering.