Skip to content
EngineerSoftware
Menu
Design
English

Engineer / Software / 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. One infrastructure plan for 14 departments

    Designed a comprehensive infrastructure framework for a research institute impacting 14 departments, featuring flexible modules, unified data pipelines, and structured support strategies for long‑term adoption.

    Designed a comprehensive infrastructure framework for a research institute across 14 departments — modular, with unified data pipelines and support strategies.

  2. Delivered 8 Power BI projects with manuals

    Delivered 8 Power BI projects with comprehensive manuals, integrating Microsoft Power BI tools with NodeJS API and Python FastAPI for effective data analytics and visualization.

    Delivered 8 Power BI analytics projects (Node.js API, Python FastAPI) with full manuals, improving report generation efficiency by 60%.

  3. Migrated the API to Huma v2 at 100% parity

    Migrated the HTTP API from Fiber to Huma v2 — 649 paths and 760 operations — reaching and holding 100% parity between the routes the server registers and the OpenAPI description it publishes.

    Migrated the HTTP API from Fiber to Huma v2 — 649 paths, 760 operations — at 100% parity between registered routes and the published OpenAPI description.

  4. 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.

  5. 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.

  6. Ran development as 51 written initiatives

    Ran the site's development as 51 written initiatives across 54 plan documents, each carrying its open boxes, its measurements and the decisions it declined — including six of eight agent‑readiness findings refused with the reason recorded.

    Fifty-one decisions with their reasoning attached, roughly three-quarters closed, and the declined ones are as retrievable as the accepted ones.

  7. Passed 106 of 106 PDF/UA‑1 profile checks

    Recorded PDF/UA‑1 validation across nine documents with 106 of 106 configured accessibility‑profile checks passing, while the archival variant failed one of 146 rules.

    All configured accessibility-profile checks passed. The archival claim is stated honestly as a near-miss with the specific gap named.

  8. Built a cross‑language figure check

    Built a cross‑language content check that fails when a translation drops a figure the English states, and when a language uses notation it does not use — finding two Danish descriptions missing a metric and sixteen Ukrainian spans quoting in the English style.

    Eighteen real defects closed and the class closed with them, since every future translation is compared to its English source before it can be committed.

  9. 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.

  10. Rewrote error messages to stop blaming users

    Rewrote the application's error messages against a written tone standard after a refused sign‑in blamed the user for mistyping when the provider actually required an app‑specific password, and covered it with a test that names the provider.

    The error surface follows a stated standard and the case that prompted it is covered by a test that fails on the old text.

  11. 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