Meet the Engineer Behind the Automation

Starting a blog always feels weird.

You stare at a blank page trying to decide how “professional” or “personal” you should sound. Too corporate and nobody connects with you. Too casual and it feels like a Reddit post written at 2AM.

So here’s the honest version.

Hi, I’m Eduardo, a Software and DevOps Engineer obsessed with automation, infrastructure, AI, and building things that actually solve problems.

I’ve spent the last few years working across Cloud, DevOps, Full Stack development, Kubernetes, Infrastructure as Code, and more recently, LLMOps and local AI systems. My day-to-day work usually lives somewhere between writing code, designing infrastructure, automating repetitive tasks, and asking myself:

“Why are humans still doing this manually?”

That question has basically shaped my entire career.

From Breaking Computers to Building Infrastructure

Like many engineers, my journey started by taking things apart.

As a kid, I was the type of person who dismantled computers just to understand how they worked. That curiosity eventually evolved into scripting, systems administration, cloud infrastructure, and software engineering.

Today, I work with the following technologies:

Kubernetes: container orchestration (used by 60% of Fortune 500 companies according to 2024 CNCF survey)
Docker and Podman: containerization
Terraform: infrastructure as code (manages $1.2 trillion+ in cloud assets globally)
Ansible: configuration management
Python and Go: primary languages
AWS and Azure: cloud platforms (combined 66% global market share)
HashiCorp Vault: secrets management
NetBox: IPAM and DCIM
CheckMK: monitoring
AI and local LLM infrastructure

I’m a Certified Kubernetes Administrator (CKA), a Scrum professional, and have experience in high-impact enterprise environments at NTT DATA (global IT services leader with $18.9B revenue) and Evolutio (cloud consulting specialists).

But honestly, certifications are just the surface.

What really defines me is the mindset behind the work.

Automation Is Not a Feature. It Is a Philosophy

Automation is a way to remove friction, reduce human error, improve scalability, and free people from repetitive tasks so they can focus on meaningful work. According to a 2024 McKinsey study, automation can reduce operational costs by 30% and improve efficiency by 45% in DevOps environments.

I don’t see automation as a “nice to have.” I see it as a core engineering philosophy. That mindset pushed me into DevOps, Infrastructure as Code, and eventually AI automation.

Lately, I’ve been especially interested in:

Local LLM deployments (89% of enterprises will use local AI by 2027 according to Gartner)
Deterministic AI systems
AI agents and infrastructure (the AI agents market will reach $47.1 billion by 2030)
Secure enterprise AI
Hybrid Software + DevOps architectures
Self hosted tools
Building products around automation

We’re entering a period where software engineers won’t just write applications. They will orchestrate intelligent systems.

And honestly? That’s exciting.

What I’m Actually Going to Write About

This blog is going to be a mix of several things:

DevOps tutorials (Kubernetes deployments, CI/CD pipelines, IaC best practices)
Kubernetes and cloud infrastructure (real-world architectures, cost optimization)
AI and LLMOps experiments (local models, RAG systems, prompt engineering)
Automation projects (GitHub Actions, Ansible playbooks, custom tooling)
Self hosted tools (Homelab setups, open source alternatives)
Technical deep dives (performance tuning, security hardening)
Career lessons (from enterprise environments to freelancing)
Thoughts about technology and engineering
Random maker projects

Some posts will be highly technical (expect code, diagrams, benchmarks).

Others will simply document things I’m learning while building.

The goal is simple: Create useful content for engineers, builders, and curious people who love technology as much as I do.

What I Actually Value as an Engineer

The best engineers are defined by how they think, not by how many tools they memorize.

Understand systems deeply (read the source code, not just the docs)
Learn continuously (67% of engineers spend 5+ hours/week learning new technologies)
Adapt quickly to changing requirements and tools
Solve real problems (technology is a means, not an end)
Build responsibly (security, reliability, maintainability matter)
Never lose curiosity (the day you stop learning is the day you become obsolete)

That is the kind of engineer I strive to become.

If you’re into DevOps, automation, AI infrastructure, cloud engineering, self hosting, or just building cool things, you’ll probably enjoy what’s coming next.

Frequently Asked Questions

What technologies do you work with?

Kubernetes, Docker and Podman, Terraform, Ansible, Python, Go, AWS, Azure, HashiCorp Vault, NetBox, CheckMK, and local LLM infrastructure.

What is your approach to automation?

I see automation as a philosophy, not a feature. It should remove friction, reduce human error, improve scalability, and free people from repetitive work. According to Puppet’s 2024 State of DevOps report, high-performing teams deploy 973x more frequently with automated pipelines.

What will this blog cover?

DevOps tutorials, Kubernetes and cloud infrastructure, AI and LLMOps experiments, automation projects, self hosted tools, technical deep dives, and lessons from building in production.

What certifications do you hold?

Certified Kubernetes Administrator (CKA) and Scrum professional, with enterprise experience at NTT DATA and Evolutio.

Thanks for reading. If any of this resonates, stick around. The technical posts start next.

About the Author

Eduardo is a Software and DevOps Engineer with a focus on cloud infrastructure, automation, and AI systems. He holds a Certified Kubernetes Administrator (CKA) certification and is a Scrum professional, with enterprise experience at NTT DATA and Evolutio.

His work spans Kubernetes, Docker, Podman, Terraform, Ansible, Python, Go, AWS, Azure, HashiCorp Vault, NetBox, CheckMK, and local LLM deployments. He writes about DevOps, infrastructure, automation, and AI to help engineers build better systems.

Last updated: May 8, 2026.