hibbins.org · projects & case studies
A long-time technology generalist. I have spent years across the whole of computing: hardware and operating systems, networks and infrastructure, backends, interfaces, and the product questions on top of all of it.
These days I build complete things end to end and run them in production. This is where they live.
$ whoami
generalist
$ uptime
up a long time, load average: curious
$ ls -1 ~/projects
preppals/ ● live
next/ ○ building
$ 01 · selected work
CAPS exam practice that feels like a game.
A free practice platform for South African learners in Grades 5 to 12. Short visual lessons, exam-style questions with instant feedback, spaced review, and progress that parents and teachers can follow. One person, every layer, running on Cloudflare's edge.
total 1
02 · the whole stack
Most products cut across every one of these layers. A generalist's job is to be competent at all of them and to know which one the problem really lives in. Each project is tagged with the layers it reached.
03 · how I work
The specialists go deep; I go across, then deep wherever the problem is. Four rules that show up in everything here:
A product fails at the seams between specialisms. Knowing the database, the network and the button lets you fix the problem where it actually is, not where your job title says it is.
An ADR or a maintainer note for every sharp edge. Future me, and whoever comes next, should never have to reverse-engineer why.
It usually is. Free tiers, static where possible, one Worker instead of a fleet. Constraints are a design tool.
Mark answers on the server, cap what the browser claims, keep private areas free of third parties, and test that it stays that way.