In this article

23 July: the job

Work on Mach began on 23 July 2026, under the name RevQ, now Mach.

The job: find the right companies, research them and their people properly, and write honestly. A person approves what goes out. Your team replies and meets.

The founder builds it with one engineer, in small steps, each with its test.

861 commits since 23 July, drawn as tests

By 17 October, Mach held 861 commits since 23 July. A commit is one saved change to the code. The tests show the pace better than the count.

By 17 October, the database had gone through 263 changes. Each is a one-way file with notes anyone can read. The database is shared with the live product, so nothing moves backward.

Java tests from 20 September to 14 October: 116 rising to 3,026.

The day the database lost its guards

On 9 October, read-only checks found the shared database missing 113 safety checks and 12,558 reference rows after a clean-up.

Two one-way change files put every one back, proven by a test, before anything else was built on top.

Nothing was fixed by hand. The repair is a file anyone can read, with its checks inside it.

Checks run before we say done

On 23 September, one change made from an old copy undid another's work across 97 files. It was put back the same day, and our habit of gates dates from then.

On 12 October, a full gate ran 496 checks, the build and 110 screenshots before a release. On 14 October, the release gate caught missing tracing before it shipped.

14 October: the name Mach

The product began as RevQ, now Mach. On 14 October we bought machgtm.com, took the new name and shipped 47 commits that day.

A new name twelve weeks in costs little. A new name a year in costs a brand.

The rules that held up

Plain words everywhere a person reads. No fact without a source. One person ships every release, so two releases never collide.

And the mistake we keep paying for: starting a new thing before finishing the last one. The fix is boring: finish one page fully, then move on.

How the method works, with failing tests first, is its own post. The dated numbers live on the author page.

Common questions

How is that pace possible?

Small steps, built by the founder with one engineer. Most changes land with their test in the same commit. The test curve, not the commit count, is the honest measure.

Where the numbers come from

Every count, date and story comes from Mach's commit history and journal since 23 July. Customers and vendors stay unnamed.