Open Source Impact · Public Recognition

The evidence, in one page.

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.

Snapshot

Consolidated metrics

As of · source: manual — run npm run metrics to refresh the GitHub section from the public API

Loading…

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

Published repositories

Permissively licensed, published with the harness that produced the numbers.

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

  • ci-cd
  • github-actions
  • developer-experience
  • shell
  • local-first
  • act

api-mock-services

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.

  • —stars
  • —forks
  • —watchers
  • —open issues

JavaScript · MIT · last push Oct 2026

  • mocking
  • offline
  • payments
  • fintech
  • testing
  • zero-dependency
  • nodejs

Public recognition

Recognition beyond the employer

Publications, releases and other records that exist outside any single company, and that a third party can verify.

  1. Open Source

    CI Kit — run your CI on your laptop, before you push

    GitHub · 2026 — MIT licensed. Ships with the evidence document and the measurement harness.

  2. Open Source

    api-mock-services — stand-ins for the outside world

    GitHub · 2026 — MIT licensed, zero dependencies, published to npm as @bytesickle/api-mock-services.

  3. Documentation

    Published documentation sites for both projects

    GitHub Pages · 2026 — Architecture, CI gates, offline testing and a community page whose adopter list is a file in the repository.

  4. Publication

    The Silent Bill: How Remote CI/CD Drift Destroys Startup Engineering Momentum

    Substack / Dev.to · 2026-09-18 — Published technical essay on CI/CD reproducibility

  5. Publication

    Architecting Local Sandboxes for Interswitch and Paystack Integrations, Completely Offline

    Substack / Dev.to · 2026-08-27 — Architecture essay on offline payment integration testing

  6. Archive

    The earlier body of published work, 2013–2025

    TechLiaison · 2013–2025 — Thirty or more articles on support, delivery, infrastructure and data, kept public and dated.

Community

The public record, and how to join it

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.
Add yourself to the adopter list Contributing
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.
Submit a mention, a talk or a write-up Contributing
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.
Contribute a mock as a file Contributing

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

Milestones and recent work

A continuous record of shipping and publishing, not a single launch.

Oct 2026 Shipped ci-kit: v1 released with the evidence document
Oct 2026 Shipped api-mock-services: v1 published, footprint gate in place
Oct 2026 Published Evidence hub — this page, and the verification index
Sept 2026 Published The Silent Bill — CI/CD drift essay
Aug 2026 Published Architecting Local Sandboxes for Interswitch and Paystack

2024–2025

The earlier archive published

Thirty or more articles on support, delivery, infrastructure as code and Docker, written for working teams rather than for a portfolio.

Read more

2026-07

Deterministic toolchain essay

Wrote up why most build-cache architectures solve the wrong problem, and what a lockfile plus a local resolver actually needs.

Read more

2026-08

api-mock-services published

One dependency-free process standing in for eighteen third-party providers, with the footprint enforced as a build gate.

Read more

2026-09

The Silent Bill published

Essay on the hidden cost of slow and unverified pipelines, cross-posted to Substack and Dev.to.

Read more

2026-10

CI Kit v1, with its evidence document

The local gate released, and the document that says how every number in it was measured — and what is not claimed.

Read more

What this record covers

The four areas this work is assessed on

Where each part of the public record sits, and the artefacts that back it.

Original published work

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.

Evidence of professional and technical competence

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.

Recognition beyond a single employer

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.

Ongoing public activity

A continuous record of shipping and publishing, evidenced by the activity log and the commit history of each repository.

Cross-pollination

Where to find the work