Kubernetes Platform LeadPlatform Strategist
Application admin to Kubernetes platform lead, learned the way most of us do — because production was on fire, not because someone wrote a curriculum. I build things, run my own infrastructure, and write for engineers who need something working, not just studied.
Start with a Pathway
All pathways →A curriculum that deliberately crosses site boundaries — one goal, several sites, in the order you need them.
Debugging With Nothing But a Terminal
The Page Comes In → Find the Signal in the Noise → The Data Is Structured, Not Just Text → Move Without Lifting Your Hands Off the Keyboard → Fix It, Track It, Ship It → Go Deeper
How Modern Software Really Runs on a CPU
The Machine Underneath → One Kernel, Many Machines → The Process Wearing a Costume → Who Decides Which CPU → How It Got There At All → Go Deeper
Deep Dives
All deep dives →Deep on one topic, start to finish, within a site you already know your way around.
Day One
All Day One →Zero assumptions — gets you oriented and productive on technology you've never touched.
Kubernetes
Gets an application developer who just got cluster access from "no idea where to start" to a deployed, understood app, via a choice of two tool paths.
Linux
Closes the gap between "I use Linux" and "I can work in it" — SSH access, orientation, permissions, safe read-only exploration, and log-reading, without becoming a sysadmin.
When the Workday Ends
Not everything is infrastructure.
SxS Adventures
Riding trails across Nova Scotia and tracking every run — GPS routes, elevation profiles, and photos from behind the wheel. Self-hosted because of course it is.
Exploring Electronics
A software engineer learning hardware the hard way — MicroPython, microcontrollers, and circuits that almost work. Very early. Very personal. No pretense of expertise.
Exploring CNC
An X-Carve 2, FreeCAD, and a lot of G-code — learning to cut real material, where bad math turns into expensive kindling instead of just a stack trace.