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.
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.
Have you thought about taking an AWS certification? If you have you might have stumbled across a learning platform called ACloudGuru?
I had thought about taking an exam for quite some time to help with various projects. But I finally got around to it and I’m currently about half way through my preparation for the AWS SysOps administrator exam using a site called ACloudGuru.
Today I wanted to talk you through some of my initial impressions using the ACloudGuru product and my motivations for taking an exam. Lastly I’ll give you some insight into the whole process to help you better understand if taking an AWS exam could be for you and whether ACloudGuru could help.
Here is my latest post for Simple Programmer…
There are many lists of books about becoming a better programmer. They likely include books like Refactoring, Code Complete, The Mythical Man Month, etc.
However, in the workplace, it isn’t just programming knowledge that we programmers need. Learning programming is an essential part of our work — but it’s not everything.
The authors of iconic programming books had remarkable careers, but it wasn’t just their coding knowledge that made their careers noteworthy. They were well-rounded experts and we should strive to emulate that quality as well.