OLD SCHOOL ENGINEERING.
MODERN INFRASTRUCTURE.
Unix. Linux. FreeBSD. Networking. Automation. Infrastructure as Code. Kubernetes. Platform Engineering.
Technology changes.
Good engineering doesn't.
ROOT // SYSTEMS is about understanding the systems underneath the abstractions.
Learn Unix before containers. Learn Linux before Kubernetes. Learn networking before service meshes. Learn systems before platforms.
The goal is not to memorise commands or collect technology badges.
The goal is to understand what the machine is doing, why it is doing it, and what happens when it stops.
The infrastructure timeline
Start with the fundamentals.
The foundation layer. Understand the operating system, the network and the tools used to control them.
The philosophy.
Processes. Filesystems. Permissions. Shells. Signals. IPC.
The kernel that changed everything.
Boot. systemd. Storage. Networking. Security. Performance.
A complete operating system.
Base system. Jails. ZFS. PF. Ports. Kernel engineering.
Packets don't lie.
TCP/IP. DNS. Routing. Firewalls. Load balancing and packet flow.
If you do it twice, automate it.
Shell. Ansible. CI/CD. Repeatable infrastructure operations.
Infrastructure becomes code.
Terraform. OpenTofu. Modules. State. Declarative infrastructure.
From machines to platforms.
Once individual systems become distributed, new problems appear: scheduling, service discovery, failure domains, state, consistency and orchestration.
The operating system for distributed systems.
Control planes. Nodes. Controllers. Networking. Storage. Scheduling.
The engineering layer between infrastructure and developers.
Internal Developer Platforms. Golden paths. Self-service. Developer experience.
Design for failure. Build for recovery.
Failure domains. HA. DR. Security. Networking. Observability.
Theory is useful. Production is the test.
Systems engineering is learned by investigating failures, breaking things deliberately and understanding what actually happens under pressure.
Break it. Investigate it. Fix it.
Hands-on failure scenarios covering Linux, networking, Kubernetes, Terraform and containers.
What production actually teaches you.
Real-world incidents, strange failures, hard lessons and engineering scars.
Systems first. Abstractions second.
Engineering philosophy, architecture, production thinking and technical depth.
Understand the layer below.
Kubernetes is easier when you understand Linux.
Containers are easier when you understand processes, namespaces and filesystems.
Service meshes are easier when you understand TCP.
Cloud networking is easier when you understand routing.
Platform engineering is easier when you understand the infrastructure underneath the platform.
Abstractions are powerful. Understanding what they hide is more powerful.
Where infrastructure is going.
Infrastructure as a product.
Build platforms that allow engineering teams to consume infrastructure safely and consistently.
Desired state over manual change.
Versioned configuration, automated reconciliation, auditable changes and predictable rollback.
Systems that can help operate themselves.
Observability, automation and increasingly intelligent agents working together.
The next operational interface.
AI-assisted troubleshooting, infrastructure automation and agentic operational workflows.
Build systems you can understand.
Build systems you can observe.
Build systems you can recover.
Build systems you can automate.
And when something inevitably breaks, know exactly where to look.