Home Practice
Practice board.
A backlog of DevOps problems that I work through one small, tested project at a time. Each ticket says what is being asked. The finished ones say what I built, how I know it works and what went wrong on the way.
The board
The tickets are written as if a small online shop's platform team sent them. The shop and the requests are made up. The code, the tests and the pipelines behind the finished tickets are real, and none of it comes from my job.
The board didn't load. The same list is in the repo on GitHub.
How a ticket is written
Every ticket is a Markdown file in the repo, and a small script checks each one before it can be merged. That is why this page can read the board straight from GitHub.
- The ask The request in a sentence or two, the way the platform team would say it.
- Why it hurts What goes wrong today, and who feels it.
- Done when On open tickets, a short list that anyone could tick or not.
- What went wrong on the way On finished tickets, the mistakes I made, not just the result.
Where this comes from
The board is read from devops-practice-board each time this site is built, every few hours. The pipeline status is checked again in your browser, and falls back to the last build if GitHub is rate limiting.
Hiring for DevOps or platform work?
I’m open to DevOps, SRE and platform engineering roles. Email is the fastest way to reach me.