TTY0 · ROOT-SYSTEMS

root@systems:~$ ./initialize

Initializing knowledge base...

Loading UNIX.................... [OK]

Loading LINUX................... [OK]

Loading FREEBSD................. [OK]

Loading NETWORKING.............. [OK]

Loading AUTOMATION.............. [OK]

Loading IaC..................... [OK]

Loading CONTAINERS................ [OK]

Loading KUBERNETES............... [OK]

Loading PLATFORM................ [OK]

System ready.

Type help to see available commands.

root@systems:~$

SYSTEMS ENGINEERING ARCHIVE

OLD SCHOOL ENGINEERING.
MODERN INFRASTRUCTURE.

Understand the systems underneath the abstractions. UNIX. Linux. FreeBSD. Networking. Automation. Infrastructure as Code. Containers. Kubernetes. Platform Engineering.

ENTER THE ARCHIVE MEET THE ENGINEER

01 / PHILOSOPHY

Technology changes.
Good engineering doesn't.

Every generation of infrastructure introduces another layer of abstraction.

Virtual machines became cloud instances. Servers became containers. Containers became Kubernetes workloads. Configuration became Infrastructure as Code. Operations became platforms.

But underneath all of it are still the same fundamentals: processes, memory, filesystems, networks, permissions, protocols, storage, failure domains and human decisions.

Understand the foundation and the abstraction becomes easier to reason about.

"

Learn UNIX before containers.
Learn Linux before Kubernetes.
Learn networking before service meshes.
Learn systems before platforms.

ROOT // SYSTEMS

02 / EVOLUTION

The infrastructure timeline

The technologies changed. The underlying engineering problems did not.

1970s

UNIX

Processes · Filesystems · Shell · Permissions

1980s

BSD

Networking · TCP/IP · Jails · ZFS

1990s

LINUX

Open source systems · Servers · Networking

2000s

VIRTUALISATION

VMware · Hypervisors · Virtual infrastructure

2000s

AUTOMATION

Shell · Python · Ansible · Configuration management

2010s

CLOUD

AWS · GCP · APIs · Elastic infrastructure

2010s

CONTAINERS

Linux namespaces · cgroups · Docker

2020s

KUBERNETES

Orchestration · Controllers · Operators · GitOps

TODAY

PLATFORM ENGINEERING

Golden paths · Self-service · Developer platforms

03 / SYSTEMS

Start with the fundamentals.

The philosophy.

The kernel that changed everything.

A complete operating system.

Packets don't lie.

If you do it twice, automate it.

Infrastructure becomes code.

Distributed systems at scale.

Infrastructure developers can use.

04 / PRACTICAL ENGINEERING

Don't just read it.
Break it.

Documentation tells you how a system is supposed to work.

Engineering teaches you what happens when it doesn't.

root@lab:~$ systemctl status nginx

root@lab:~$ ss -lntup

root@lab:~$ tcpdump -ni eth0

root@lab:~$ kubectl describe pod

root@lab:~$ terraform plan

root@lab:~$ ./fix-the-problem

05 / WAR STORIES

Production doesn't care
about your documentation.

Real incidents. Real failures. Real lessons.

VIEW ALL STORIES →

The Server That Wouldn't Die

When the process keeps coming back, find out who is actually responsible.

When DNS Wasn't DNS

The name resolved. The application still couldn't connect.

The Friday Kernel Upgrade

There is always a reason to reboot. Sometimes there is also a reason not to.

06 / LABS

Theory is useful.
Broken systems teach more.

Hands-on exercises designed around the problems infrastructure engineers actually encounter.

Break it. Investigate it. Fix it. Understand why it broke.

07 / THE ENGINEER

SYSTEMS ENGINEER · ARCHITECT · BUILDER

Behind the systems
is an engineer.

ROOT // SYSTEMS is built around decades of infrastructure engineering experience.

From UNIX and Linux systems to networking, virtualisation, cloud infrastructure, automation, containers, Kubernetes and platform engineering.

VIEW ENGINEER PROFILE →

root@systems:~$ history

01 understand

02 automate

03 observe

04 troubleshoot

05 simplify

06 repeat

root@systems:~$ _