Learn DevOps From Someone Who's Been There
Real infrastructure automation taught by practitioners who've debugged production systems at 3 AM. We skip the buzzwords and teach what actually works when things break.
See Our Approach
Why Most DevOps Training Falls Short
Here's what bugs me about typical training programs. They teach you commands, show you dashboards, and send you off with a certificate.
But nobody explains why Kubernetes might be overkill for your project. Or how to handle that moment when your CI pipeline breaks at 5 PM on Friday.
You end up memorizing tools instead of understanding systems. And that's not how real infrastructure works.
What We Actually Teach
We focus on building mental models. How do containers actually work under the hood? What happens during a deployment that nobody tells you about?
- Infrastructure patterns that survive production chaos
- Debugging approaches that work when logs aren't helpful
- Automation scripts that don't break on edge cases
- Monitoring strategies that catch issues before users do
Our autumn 2025 cohort starts with fundamentals and builds toward managing real environments.
Henrik Sørensen
Lead Infrastructure Engineer
Learning From Actual War Stories
Henrik spent seven years scaling systems at mid-sized companies. The kind where you're responsible for everything and "it works on my machine" isn't an acceptable answer.
He's dealt with database migrations that went sideways. Rebuilt monitoring after complete system failures. Automated deployments that initially made things worse before getting better.
That experience shapes how he teaches. You won't just learn what to do when everything's perfect. You'll learn what to do when the deployment fails, the rollback doesn't work, and your team is waiting for answers.
Container Orchestration
Docker and Kubernetes from the ground up, including the parts that confuse everyone at first.
CI/CD Implementation
Building pipelines that handle real-world complexity, not just happy-path scenarios.
Infrastructure as Code
Writing Terraform and Ansible that teams can maintain without constant firefighting.
Production Debugging
Finding issues when standard troubleshooting steps lead nowhere.
How The Program Actually Works
Start With Systems Thinking
Before touching tools, we build understanding. How Linux processes work. What networking actually does. Why things fail in specific ways.
Build Infrastructure Step by Step
You'll provision servers, configure services, and automate deployments. Each week adds complexity based on what you've already built.
Break Things on Purpose
We intentionally create failures so you learn recovery under guidance. Better to panic in class than during your first production incident.
Work on Realistic Projects
No toy applications. You'll manage environments with databases, caching layers, and actual traffic patterns that stress your infrastructure.
Debug With Mentorship
When you're stuck, we don't just give answers. We show you how to investigate, what questions to ask, and how to narrow down causes.
Document Your Decisions
Every infrastructure choice needs justification. You'll learn to explain trade-offs to teammates who aren't technical.
Eight Months From Basics to Capable
Our next cohort runs September 2025 through April 2026. Two evening sessions per week, plus weekend labs when you need infrastructure that stays up longer than a few hours.
Foundation Phase
Months 1-2
Linux administration, shell scripting, networking fundamentals, and version control. The stuff you need before anything else makes sense.
Automation Phase
Months 3-4
Configuration management with Ansible, infrastructure as code with Terraform, and building your first CI/CD pipelines that don't constantly break.
Container Phase
Months 5-6
Docker internals, container networking, Kubernetes fundamentals, and service mesh concepts. We take it slow because this part confuses everyone initially.
Production Phase
Months 7-8
Monitoring and alerting, incident response, capacity planning, and managing a complete application stack through deployment cycles.
What Hands-On Actually Looks Like
