From Barracks to Cloud: How Military Discipline Optimizes Modern Infrastructure

Technology and a military career may seem like distant worlds at first glance. On one side, lines of code, virtual servers, and automation; on the other, hierarchy, rigorous procedures, and field operations. However, after three decades of military service, upon migrating to the DevOps and Cloud ecosystem, I realized that the foundations of both are identical: method, predictability, and resilience.

In this article, I share how the principles that guided my career in the Military Police have become my greatest allies in managing critical infrastructures.

1. Standard Operating Procedure (SOP) and Infrastructure as Code

In a military environment, improvisation is the shortest path to failure. Everything is guided by Standard Operating Procedures (SOPs) and Standard Administrative Procedures (SAPs) to ensure the mission is accomplished, regardless of who is in command.

In the DevOps world, I found the perfect equivalent in Infrastructure as Code (IaC). When we use tools like Terraform, we are essentially writing the "Operations Manual" for our infrastructure. The discipline of not making manual changes ("ClickOps") and ensuring that every resource is versioned and documented is what separates an unstable environment from an operation of excellence.

2. Crisis Management and High Availability Culture

One of the most valuable lessons I brought from the Military Police is the ability to remain calm under pressure and act based on contingency plans. In the Cloud, this translates into designing architectures with failure in mind.

The mindset is the same: what will we do if Plan A fails? A system's resilience is not a matter of chance, but of meticulous planning that anticipates the worst-case scenario to ensure the service never stops.

3. Security: The Virtual Perimeter

In the barracks, physical security and access control are fundamental. In the Cloud, the perimeter is logical. My transition to IAM (Identity and Access Management) and network security was natural, as I understand that security is not an additional feature, but the foundation of any project. Applying the "least privilege" principle is, for me, a matter of doctrine.

4. The Pursuit of Continuous Improvement

Military service taught me that study must be a daily routine. Technology evolves at a frantic pace: from physical servers to Serverless, from Docker to Kubernetes. Maintaining a routine of labs, certifications, and technical reading is not just a market necessity; it is a habit of discipline that I carry with me.