IaC Adventures: A Developer and an Infra Engineer Walk into a Cloud


Today, we’re delving once again into the fascinating world of Infrastructure as Code (IaC). It’s a tale of two tribes – developers and infrastructure engineers – each wielding their unique set of skills in the realm of code. But here’s the catch: when the “real” development skills are missing, things can get dicey.

For Developers: Coding Wizards of the Digital Realm

Developers, you’re the maestros of code, sculpting software like Michelangelos of the digital world. But when you move into IaC territory, it’s a different ballgame. Your coding skills are your sword and shield, but the landscape is ever-changing.

1. Logic: You’re no strangers to logic and algorithms. IaC requires a logical mindset to map out complex infrastructures. Without this, your castle in the cloud could crumble.

2. Details: Attention to detail is your forte. In IaC, a single misconfiguration can lead to chaos. Precision is your ally; lack of it, your nemesis.

3. Testing: Testing is your ritual. It’s how you ensure your software functions flawlessly. In IaC, those tests are your compass in the uncharted cloud waters.

4. Adaptation: The tech world evolves, and you evolve with it. IaC requires adaptation – learning new tools and techniques, just like you did with software frameworks.

For Infrastructure Engineers: Architects of the Digital Landscape

Now, let’s welcome the infrastructure engineers. They’re the architects of the digital landscape, with expertise in networking, systems, and hardware. But when coding enters the scene, it’s a whole new story.

1. Networking: You’re the grandmasters of networking, routing, and subnets. In IaC, you’re translating these skills into the language of code, building virtual highways in the cloud.

2. Systems: Operating systems and hardware obey your command. In IaC, you’re scripting the behavior of these elements, orchestrating a digital symphony.

3. Configuration: Configuration isn’t a chore; it’s your art. IaC amplifies this skill – databases, storage, and security settings are your canvas, and code is your brush.

4. Security: Fortifying systems is your specialty. In IaC, you’re the guardian of the cloud, ensuring firewalls, access controls, and encryption are seamlessly integrated.

Ah, here’s the twist – when either tribe lacks “real” development skills, the code suffers. For developers, IaC can become a tangled web of misconfigurations, like software riddled with bugs. For infrastructure engineers, the coding journey can feel like entering unknown realms without a map.

Without strong coding skills, infrastructure code becomes fragile. Missteps in logic, errors in syntax – they all lead to instability. The cloud kingdom you build may look magnificent, but its foundation is shaky.

Bridging the Gap: The Solution Lies Within

The solution? Collaboration, of course. Developers and infrastructure engineers must share knowledge. Developers can bring their coding skills to the infrastructure table, enhancing stability. Infrastructure engineers can share their understanding of systems and networking.

In the end, IaC is a playground where developers and infrastructure engineers meet, code, and conquer. The difference in skills is a challenge, but it’s also an opportunity to learn and grow. So, whether you’re coding a castle or scripting a network, remember – IaC thrives when the two tribes unite, building a digital world that’s both powerful and resilient.

Paul Muller


I joined Sogeti in 2022, after working as a Microsoft .Net developer and Azure architect in retail and the energy sector among others for over 20 years. Combining Cloud infra with Cloud applications in integrated environments is what I love most, hands-on delivering scalable and resilient solutions. As an architect I believe it is important to be able to build your own designs, as well as explain them to (business) colleagues.

More on Paul Muller.

Related Posts

Your email address will not be published. Required fields are marked *