ci-kit
Run your CI on your laptop, before you push. A local gate that mirrors what the GitHub Actions workflow does, and runs the workflow itself locally through act.
- —stars
- —forks
- —watchers
- —open issues
Shell · MIT · last push Oct 2026
Open Source Impact · Public Recognition
This page collects, in one place, the public record of my work: published software with measured outcomes, a published account of how those measurements were taken, and long-form writing on specific technical subjects. Every entry links to the artefact that supports it, so nothing here has to be taken on trust.
Open-source stars
—
How many people have starred the projects on GitHub — the public 'this looks good' button.
Forks
—
How many people have copied a project to work on themselves.
External contributors
—
How many people other than me have written code in the projects.
Followers
—
How many people follow the GitHub account to see what gets published.
Open-source tools published
2
How many complete tools are published and free to use.
GitHub
Published measurement documents
1
How many documents record exactly how a number was measured.
ci-kit/docs/EVIDENCE.md
Footprint enforced as a build gate
100 MB
The size limit the software must stay under, checked automatically on every build.
api-mock-services
Third-party providers mocked
18
How many outside services the test suite can stand in for.
api-mock-services
Published releases
2
How many tagged, versioned releases with written notes.
GitHub
Technical essays, 2026
4
How many long articles written this year for a specialist audience.
This site
Articles in the earlier archive
30+
How many articles were published in earlier years and kept online.
TechLiaison
Live documentation sites
2
How many of the projects have their own published documentation.
GitHub Pages
Open Source
Permissively licensed, published with the harness that produced the numbers.
Run your CI on your laptop, before you push. A local gate that mirrors what the GitHub Actions workflow does, and runs the workflow itself locally through act.
Shell · MIT · last push Oct 2026
Stand-ins for the outside world: the payment gateways, the identity checks, the email provider, the accounting service, the DNS provider, the messaging, the AI and storage services. One implementation, used by every project.
JavaScript · MIT · last push Oct 2026
Public recognition
Publications, releases and other records that exist outside any single company, and that a third party can verify.
Open Source
Open Source
Documentation
Publication
Publication
Archive
Community
Everything here is a file in a repository and grows by pull request — so it is public, reviewable, and impossible to inflate.
Open a pull request against ADOPTERS.md adding a row: who you are, what you use the mocks for, and the year. That is the whole process. If you would rather not be listed, that is completely fine — the list exists for the people who want to be found.
Links to blog posts, talks, newsletters and social posts about a project belong in the community page's mentions table, and they are added by opening an issue with the URL. A link can be checked in one click, which is why the projects collect links rather than testimonials.
The mock engine takes a contributed mock as a route file with no code in it, under contrib/. The test suite starts one, checks it answers, and fails if it does not — so a new provider is a small, reviewable pull request rather than a change to the engine.
The adopter list is a file in the repository, and it grows by pull request. That makes it public, reviewable and impossible to inflate — a name on that list is a commit anyone can see and revert. Adding yourself takes a pull request and a row; there is no form, no email and no account.
Ongoing activity
A continuous record of shipping and publishing, not a single launch.
2024–2025
Thirty or more articles on support, delivery, infrastructure as code and Docker, written for working teams rather than for a portfolio.
Read more2026-07
Wrote up why most build-cache architectures solve the wrong problem, and what a lockfile plus a local resolver actually needs.
Read more2026-08
One dependency-free process standing in for eighteen third-party providers, with the footprint enforced as a build gate.
Read more2026-09
Essay on the hidden cost of slow and unverified pipelines, cross-posted to Substack and Dev.to.
Read more2026-10
The local gate released, and the document that says how every number in it was measured — and what is not claimed.
Read moreWhat this record covers
Where each part of the public record sits, and the artefacts that back it.
Three open-source tools under permissive licences: a local CI gate, a dependency-free mock engine for third-party APIs, and an air-gapped automation platform. The first two ship with the harness that produced their measurements, so the performance claims can be independently reproduced.
A published evidence document that shows how each number was taken, discloses the measurement that was discarded, and has a dedicated section listing the claims that are not made. A platform whose architecture is checkable by reading its layout rather than by trusting a benchmark.
A dated body of published writing spanning 2013 to 2026, addressed to working engineers rather than to an employer, plus live documentation sites and public repositories for each project.
A continuous record of shipping and publishing, evidenced by the activity log and the commit history of each repository.
Cross-pollination