new post: The capacity check that let all nine through

Wilhelm Maritz
I build the systems that keep operations running: automation, dashboards, and backend services.
- I work in BI, automation, and operational systems.
- Most of my time goes on the backend now: Flask, APIs, and data.
- I care about reliability, ownership, and code that holds up.
I came to software the long way round. For years I worked in healthcare operations, where the margin for error was thin. Somewhere in there I started automating the parts that kept breaking, and the building never stopped.
These days the work is mostly backend: pulling messy data into something coherent, designing dashboards people actually use, and wiring up workflows that run without anyone babysitting them. The interesting problems are rarely the happy path. They are the edge cases and the failure modes.
It is one thing to make something work once; it is another to make it auditable, documented, and safe to hand over. A long stint working under operational pressure, plus a clinical and management background, taught me to design for the day things go wrong rather than the day they go right.
Right now I am going deep on backend development through the boot.dev track: Python, data structures and algorithms, Linux, and a bit of C for the memory-management fundamentals. I build to understand things from the ground up, and I would rather ship a practical solution than talk about one. On the side, I am chipping away at German.
Recent posts
- The capacity check that let all nine throughNine writers hit one limited slot at the same moment and all nine got on. The capacity check ran for every one of them, the lock was the right lock, and a one-user test passes it every time.
- The graphs came back, and that proved nothingI moved Grafana and Prometheus to a new VM and every panel drew straight away. A graph only draws what's there. It can't tell you what's gone.
- The diagrams carried the argument, and screen readers got none of itNearly every post on this site opens with a diagram that does the explaining. For as long as the site has existed, not one of those diagrams had alt text, and the theme I'd picked had left nowhere to put it.
- My deploy ran my tests, and my tests ran my deployMy desktop ran out of memory five times in two days, once killing 29,082 processes at a stroke. Two files that were each sensible on their own had made a loop with no way out.
Skills
languages
- PythonPrimary language. Day-to-day scripting, automation, and backend work.
- PowerShellGo-to for Windows automation and glue scripting.
- JavaScriptWorking knowledge for front-end behaviour and small interactive pieces.
- CLearning the fundamentals: memory management and how things work closer to the metal.
backend & web
- FlaskMain backend focus. Building APIs and small web apps while learning the patterns that keep them maintainable.
- SQLAlchemyThe ORM behind my production Flask apps, and knowing when to step around it on hot read paths.
- SQLiteRunning in production behind real users, with nightly off-site backups.
- HTML & CSSHand-written markup and styling for responsive layouts, reaching for Bootstrap when speed matters.
automation
- Power Automate & Power AppsApproval flows, process automation, and low-code apps across the Microsoft 365 stack.
- n8nRunning self-hosted on my homelab and on Railway, for automation outside the Microsoft stack.
data
- Power BIBuilding dashboards and reporting that people come back to.
- ETL & data modellingDesigning data models and pipelines that turn scattered sources into a single, queryable store.
infra
- Linux & WSLDaily working environment; comfortable on the command line and writing Bash.
- Git & GitHubVersion control for everything.
- DockerContainerising apps for consistent local and deployed environments.
- RailwayWhere my production Flask apps run, and whose GraphQL API feeds my own metrics.
- Prometheus & GrafanaMy own monitoring stack: dashboards generated from Python, and exporters I wrote for services that don’t export metrics.
- Proxmox VEA ZFS-backed host for my homelab VMs, with nightly backups I’ve tested by restoring one.
- Cloudflare TunnelsExposing self-hosted services safely without opening inbound ports.
- TailscalePrivate access to my homelab from my own devices, wherever they are, with nothing exposed to the internet.
Projects
Paul Newman Cup
read morePurpose: an inter-team fitness and sports competition where teams score across four pillars.
Key features: Strava sync and verification for runs, rides, and swims, officials capturing monthly results, and role-controlled administration.
Stack: Flask, SQLAlchemy, SQLite in WAL mode, Firebase sign-in, Strava OAuth, on Railway behind gunicorn.
The design splits identity from permission: Firebase proves who you are, but the app’s own database decides what you can do, including an account kill-switch that takes effect on the very next request. Because the app is server-rendered, the session rides in a secure HttpOnly cookie rather than a bearer token, which would need client-side JavaScript to attach it to every request.
railway-bridge
source on githubPurpose: Railway shows a service’s requests, latency and resources in its dashboard but exports none of it, so a Flask app I maintain there was the one blank spot in my Grafana.
What it does: one Python file, standard library only, polls Railway’s GraphQL API every five minutes and serves Prometheus metrics: requests by status class as a real counter, latency percentiles, CPU, memory and disk against their limits, 7-day totals, and the last 20 deploys with their version and change.
The hard part was the counter. Railway hands back per-minute figures, the newest minute is still filling in, and polls overlap, so it keeps a high-water mark per status code and only counts a minute once it has ended. Checked against Railway’s own figures: 9,344 of 9,344 requests over 21 hours. Written up in Railway shows my request counts but won’t export them.
kuma-monitors
source on githubPurpose: Uptime Kuma has no config file, so monitors clicked into its web UI can’t be reviewed, diffed or rebuilt.
What it does: declares the monitors, groups, status page and ntfy notification in Python and creates them over Kuma’s API. It is safe to re-run: it matches by name and skips what already exists.
Its guard came from a real gap: Kuma’s “default” and “apply to existing” settings don’t attach a notification to monitors created later over the API, and for two days none of mine could alert. The script now attaches the notification to every monitor and refuses to finish while any monitor is left silent. Written up in The 03:37 alert that was never sent.
Homelab
read moreThe NAS: a ZimaBoard 2 running ZimaOS, with a RAID1 mirror (2 x 4 TB, BTRFS) holding photos in Immich, documents in Paperless-ngx, backups and personal archives. Services are reached through Cloudflare Tunnels and Tailscale rather than open ports.
The server beside it: a GMKtec K10 running Proxmox VE on ZFS, with one VM for my AI agents, kept off the NAS, and one for services: Grafana and Prometheus, fed by exporters I wrote, and Portainer. The VMs back up nightly to the mirror, and I restored one before trusting the backups.
Watching it: Uptime Kuma, declared in code, alerts my phone through ntfy.
The sharpest lessons have come from storage: a migration once filled the system disk and left the storage layer unable to cleanly reattach the array, which taught me to treat the OS as disposable and the data as authoritative, and to rebuild from a verified backup rather than chase a half-recovered state.
Property analytics workbook
A spreadsheet model for analysing residential buy-to-let investments across financing, cash flow, and tax treatment, used to compare prospective deals on a consistent basis. Built in Excel and Google Sheets.