Skip to content
EngineerPlatform
Menu
Design
English

Engineer / Platform / Services

Writing it down so the next person can follow

Handovers, runbooks and manuals that let your own staff operate the system without ringing whoever built it.

  1. Authored 578 go‑task automation targets

    Authored 578 go‑task automation targets spanning native, Docker and HTTPS dev modes, linting, testing, database and deployment.

    Authored 578 go-task automation targets across native, Docker and HTTPS modes — linting, testing, database and deployment behind one toolchain.

  2. Built a 268‑check guard engine for the repo

    Built the repository's guard engine — 268 registered commit checks, 277 lint rules and 15 custom ESLint rules — plus 146 tests of the guards themselves, so the build holds the standard, not review.

    Built a guard engine of 268 registered commit checks, 277 lint rules and 15 custom ESLint rules, with 146 tests of the guards themselves.

  3. Ran a continuous security scanning programme

    Established a continuous security programme — code scanning, DAST, dependency and vulnerability checks, SBOM generation, secret scanning and SHA‑pinned actions — alongside 21 written security audits.

    Established a continuous security programme — code scanning, DAST, dependency checks, SBOM, secret scanning and pinned actions — plus 21 audits.

  4. Built 7 read‑only host reporting roles

    Built seven read‑only reporting roles that render a live host to Markdown — facts, access, git, metrics, traffic, security and provider inventory — under a rule that no number is printed the run did not measure.

    The estate can be described from the repository on demand, and the reports have found real things: the two dead security controls, an undeclared listening…

  5. Wrote a scope rule after a credential leak

    Wrote a scope rule into the repository after a restructure carried another company's inventory, firewall allowances and prose into it — and kept the quarantined residue under the secret scanner rather than excluding it.

    The scope boundary is a written rule with a stated test, the residue is visible rather than buried, and the specific shape of credential that got through now…

  6. Built a 22‑linter commit gate

    Built a commit gate of 22 one‑line linters plus five that earn a paragraph, with no warning tier and no inline suppressions permitted, covering HTML, CSS, JavaScript, Python, YAML, Markdown, shell, links, spelling, secrets and typography.

    Mechanical objections are made by a machine before a commit exists, and the gate is the only reviewer this project has.

  7. Found the hooks and the gate disagreeing

    Found the commit hooks and the quality gate running different checks while a document promised they were the same, by comparing the two lists in a test — the five that only ever ran by hand were the ones reading the CV prose.

    The hook and the gate provably run the same checks, and the prose checks now run on every commit.

  8. Wrote a parser verifying every FFI call

    Wrote a parser that reads the real 7,308‑line C header and verifies every call site, every enum constant and that every pointer‑owning class is final, after a hand‑written placeholder header let calls to three removed functions compile, link and crash.

    The class of defect that produced the original crash cannot recur, because a stale reference is now a build failure rather than a runtime one.

  9. Held 4 repositories to one history standard

    Held four repositories to one history standard — conventional, emoji‑free, no attribution trailers, enforced by a commit‑message hook — alongside 48 instruction documents that govern how the work is done.

    Four repositories share one history format and one instruction structure, both enforced by hooks rather than by discipline.

  10. Made six collectors state what they skipped

    Made six reporting collectors state the part of their input they never read — files that stayed shut, probes not installed, journal lines unrecognised — and fitted thresholds to 116 measured samples, after establishing that a blind collection and a healthy host render the same page.

    A page of this platform's numbers now carries its own blind spots beside its findings. None of the self-measurement is a gate, and that is stated rather than…

Contact

Still working out what you need?

Tell us what is going wrong, or what you are trying to build. We will tell you what it would take, roughly what it would cost, and whether we are the right people for it.

From 1,400 DKK an hour, excluding VAT — and less per hour on a longer booking.

welcome@engineer.company +45 50 10 61 84 Copenhagen, Denmark