Skip to content
Engineer
Menu
Design
English

Engineer / Categories

Automation & CI/CD

  1. 30 days of electricity data in 180 ms

    Engineered hourly electricity‑consumption aggregation variants in Python, SQL and Bash + Jq, with the Python benchmark processing one 30‑day JSONL dataset in 180ms.

    Built and benchmarked electricity-consumption aggregation in Python, SQL and Bash + Jq; Python processed a 30-day JSONL dataset in 180 ms.

  2. Resolved 1,000 issues in geographical data

    Resolved 1,000 issues in geographical data and time‑series data, using GDAL, ArcGIS, PostGIS, Mapbox, QGIS, SQL (PL/pgSQL, Transact‑SQL), Bash, ensuring high‑quality big data processing.

    Resolved 1,000+ issues in geographic and time-series big data with GDAL, PostGIS, ArcGIS, Mapbox, QGIS and SQL — 35% faster queries.

  3. Designed and ran 6 ETL/ELT pipelines

    Designed, implemented, and administered 6 ETL/ELT pipelines, utilizing Google BigQuery, MSSQL, PostgreSQL, Shell scripting, PL/pgSQL, and Transact‑SQL, integrating data for efficient Python API processing.

    Designed and ran 6 ETL/ELT pipelines (BigQuery, MSSQL, PostgreSQL), cutting a 3-hour manual job to under 20 minutes with daily syncs.

  4. Built the company's first observability dashboard

    Developed and launched the company's first observability dashboard, providing real‑time system performance insights and data visualization on the large office TV.

    Built the company's first observability dashboard for real-time system insight, helping teams detect and resolve incidents 40% faster.

  5. Ran 10 PostgreSQL and MS SQL servers on Ubuntu

    Designed, deployed, and maintained 10 PostgreSQL and MS SQL servers on Ubuntu Linux VPS, ensuring optimal server performance and reliability.

    Designed and maintained 10 PostgreSQL and MS SQL servers on Ubuntu Linux VPS at 99.9% uptime, with 30% faster queries via tuning.

  6. Wrote 1,000 RBAC rules to secure Linux servers

    Enhanced data security by implementing 1,000 RBAC rules for developers, application instances, PostgreSQL, MS SQL, and other Linux servers, preventing unauthorized access; documented with Ansible automation.

    Implemented a recorded 1,000 RBAC rules across developer, application, database and Linux access, with documented Ansible configuration.

  7. Automated GIS SaaS deployment with GitHub Actions

    Automated GIS SaaS application deployment, data processing, and reporting system using GitHub Actions CI/CD, Python, Bash, and SQL.

    Automated GIS SaaS deployment, data processing and reporting with GitHub Actions CI/CD, Python, Bash and SQL — shorter, reliable releases.

  8. Automated delivery of 20 GIS data pipelines

    Automated delivery of 20 GIS data pipelines and app data ETL processes, streamlining infrastructure automation and reporting.

    Automated 20 GIS data pipelines and app-data ETL processes, streamlining infrastructure automation and delivering dependable, current data.

  9. Automated 100 critical data backups using Barman

    Automated 100 critical data backups using Barman, Google Cloud, Bash, and Python, ensuring data integrity across databases.

    Automated 100 critical database backups with Barman, Google Cloud, Bash and Python — turning data recoverability into a tested fact.

  10. Ran 20 Docker apps on Google Cloud and AWS

    Deployed and maintained 20 Docker containerized applications, troubleshooting with Podman and Kubernetes, and managing R‑based apps on Google Cloud and AWS.

    Deployed and maintained 20 Docker containerized apps across Google Cloud and AWS, troubleshooting with Podman and Kubernetes for stable releases.

  11. Led access management across M365 and SSO

    Prevented security breaches by leading access management initiatives, utilizing M365, 1Password, Red Hat SSO, and OKTA SSO.

    Led access management with M365, 1Password, Red Hat SSO and OKTA, sharply cutting unauthorised-access risk and making access auditable.

  12. Cut operational risk with Grafana and Prometheus

    Mitigated operational risks by implementing a monitoring dashboard using Grafana and Prometheus, improving system reliability.

    Built a Grafana + Prometheus monitoring dashboard that catches problems before they escalate, shifting the team from firefighting to prevention.

  13. Improved team communication and collaboration

    Improved team communication and collaboration by implementing Slack, Mattermost, 1Password, and Jira, saving 8,000 hours of labor.

    Saved ~8,000 hours by rolling out Slack, Mattermost, 1Password and Jira, turning chased information and redone work into real delivery.

  14. Overhauled internal processes, saving 8,000 hours

    Overhauled internal processes, saving 8,000 hours by improving software architecture, systems, and scheduling efficiency.

    Overhauled internal processes to save ~8,000 hours, improving software architecture, systems and scheduling efficiency.

  15. Administered network infrastructure

    Administered network infrastructure for over 1,000 servers, ensuring optimal system deployment, security, and troubleshooting.

    Administered network infrastructure for 1,000+ servers, ensuring reliable deployment, solid security and prompt troubleshooting.

  16. Automated SSL/TLS certs for 100 Docker apps

    Automated SSL/TLS certificate creation for 100 Docker applications, ensuring secure connections across Ubuntu Linux hosts.

    Automated SSL/TLS certificates for 100 Docker apps on Ubuntu Linux, ending manual renewals and the outages expired certs cause.

  17. Streamlined CI/CD processes, saving 4,000 hours

    Streamlined CI/CD processes, saving 4,000 hours by introducing automation in software development pipelines.

    Streamlined CI/CD to save ~4,000 hours, making releases faster and more reliable so the team could ship with confidence.

  18. Saved 4,000 hours with GitHub and GitLab CI/CD

    Streamlined data analysis and software development processes, saving 4,000 hours by introducing GitHub, GitLab, Bash, and Python CI/CD practices.

    Saved ~4,000 hours by introducing GitHub, GitLab, Bash and Python CI/CD, speeding data analysis and development while adding consistency.

  19. Developed a Data Analytics reporting system

    Developed a Data Analytics reporting system, increasing quarterly software revenue by 400% through Python‑based PDF reports.

    Built a Python data-analytics reporting system that raised quarterly software revenue by 400% with clear, timely PDF reports.

  20. Automated data processing in Python and PL/pgSQL

    Automated data processing tasks using Shell scripting, PL/pgSQL, Python, and Transact‑SQL, increasing productivity and efficiency.

    Automated data-processing tasks with Shell, PL/pgSQL, Python and Transact-SQL, lifting productivity and ending small recurring errors.

  21. Saved 150 hours a month across 30 projects

    Enhanced project efficiency, saving 150 hours per month across 30 projects by optimizing workflows and resource management.

    Saved ~150 hours per month across 30 projects by optimising workflows and resource management — a recurring, portfolio-wide gain.

  22. Engineered 600 PL/pgSQL ETL/ELT pipelines

    Engineered 600 PL/pgSQL‑based ETL/ELT pipelines to streamline complex data processing workflows across multiple PostgreSQL development and production environments.

    Engineered a recorded 600 PL/pgSQL ETL/ELT pipelines across PostgreSQL development and production, including incremental loading and logging.

  23. Generated the API contract from the database out

    Generated the API contract outward from the database — OpenAPI, a 44,076‑line typed TypeScript client, 61 mock handlers and the limits the UI enforces — with a guard at every hop that fails on drift.

    Generated the API contract from the database outward — OpenAPI, a typed TypeScript client, mock handlers and UI limits — with a guard at every hop.

  24. Provisioned Azure infrastructure as code

    Provisioned Azure infrastructure as code with Bicep — Container Apps, PostgreSQL Flexible Server, Front Door/WAF and networking — across the development, staging and production environments.

    Provisioned Azure infrastructure as code with Bicep — Container Apps, PostgreSQL, Front Door/WAF — reproducible across dev, staging and prod.

  25. Built GitHub Actions CI/CD pipelines

    Built GitHub Actions CI/CD pipelines with a distroless production frontend image and multi‑environment promotion.

    Built GitHub Actions CI/CD with a distroless production frontend image and multi-environment promotion, making releases routine and boring.

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

  27. Owned end‑to‑end platform deployments to Azure

    Owned end‑to‑end deployments of the platform to Azure, managing releases across development, staging and production environments.

    Owned end-to-end Azure deployments, moving releases through dev, staging and production along a defined, repeatable path.

  28. Built an English/Danish i18n system

    Established an English/Danish internationalization system carrying 12,027 messages per locale across 458 namespace files, with linter‑enforced vocabulary and a 400‑line budget per file.

    Established an English/Danish i18n system carrying 12,027 messages per locale across 458 files, with linter-enforced vocabulary and a size budget.

  29. Set a zero‑warnings bar across six languages

    Set a zero‑warnings quality bar across six languages — Go, TypeScript, SQL, Python, Shell and Markdown — enforced by pre‑commit hooks.

    Set a zero-warnings quality bar across Go, TypeScript, SQL, Python, Shell and Markdown, enforced by pre-commit hooks.

  30. Designed a time‑management and reporting system

    Designed a time‑management and reporting system that remained in production use for years without significant modification.

    Designed a time-management and reporting system that stayed in production for years without significant modification.

  31. Automated team collaboration

    Automated team collaboration, password management, task and time management, and built a semi‑automatic project‑showcase system, raising team productivity.

    Automated collaboration, password, task and time management and built a semi-automatic project-showcase system, raising team productivity.

  32. Integrated a company‑wide password manager

    Integrated a company‑wide password‑management system, strengthening security and streamlining access control.

    Integrated a company-wide password-management system, strengthening security and streamlining access control across the organisation.

  33. Built a test suite across Go, SQL and browser

    Built a layered automated test suite — 981 Go tests, 543 frontend and browser specs, 494 SQL behavioural tests — with mutation testing, property‑based tests and an accessibility gate.

    Built a layered automated test suite — 981 Go tests, 543 frontend specs and 494 SQL behavioural tests — with mutation, property and accessibility gates.

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

  35. Moved slow work onto a River job queue

    Moved slow work off the request path onto a River job queue — 15 worker modules, 8 scheduled tasks and 20 pg_cron jobs — so a request returns while the work behind it carries on.

    Moved slow work off the request path onto a River job queue: 15 worker modules, 8 scheduled tasks and 20 pg_cron maintenance jobs.

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

  37. Infrastructure defined in a repository

    Built the company's own infrastructure as 19 Ansible playbooks and 34 roles across 12,065 lines of YAML, converging a live host to a declared state with every play idempotent.

    The repository supplies the configuration for rebuilding the declared environment, and the parts of it that were only ever true because somebody remembered…

  38. Hardened SSH to 24 validated directives

    Hardened SSH to 24 asserted directives with three‑stage validation — the candidate file, the assembled config, then the daemon's own read‑back — after the read‑back caught the running server silently overriding two of the twenty‑four.

    The SSH posture is now the daemon's answer rather than the repository's claim, and the difference is not theoretical — it was already two settings wide when…

  39. Proved the intrusion ban works every run

    Proved the intrusion‑banning path end to end on every hardening run by banning a reserved test address, reading the resulting kernel rule and unbanning in a guaranteed cleanup block, so a jail that stops working fails a run instead of reporting healthy.

    A banning path that stops working now fails a converge instead of continuing to report healthy, which is the only property that mattered.

  40. Verified firewall rules by position

    Verified firewall rules by position rather than presence, reading the numbered rule list and the live packet‑filter chain, because a rule that exists is not a rule any packet reaches.

    The firewall posture is now checked the way a packet experiences it. The most useful outcome was not the check but what it revealed about the reporting that…

  41. Backup automation with an explicit restore method

    Implemented restic backup automation with retention, integrity checks and a monthly restore‑test workflow; documented storage activation and live‑restore verification as separate operational steps.

    The repository contains the backup and restore-test implementation and documents its activation prerequisites.

  42. Built dead‑man's‑switch host monitoring

    Built dead‑man's‑switch monitoring that pings only while memory and disk are healthy, so a degraded host raises an alert by going silent — and caught six variable names saying "free" where the check correctly measured "available", an order of magnitude apart on a 464 MB box.

    The host gained an alarm that fires when the expected signal is absent, and the misleading names were corrected.

  43. Made Ansible check mode tell the truth

    Made check mode tell the truth across the whole platform after finding six probes deciding on a value the host never gave, because Ansible's command module reports success under --check while skipping the command entirely.

    A dry run now either measures something or says it did not, and neither of those is the third option it used to have.

  44. Added a one‑second preflight for secrets

    Added a preflight play that runs the same code as the converge against operator‑local secrets in about a second, after a half‑applied production run died on its ninth task with the swap settings already written to the live host.

    A secret that does not resolve now costs a two-second refusal on a laptop instead of a partly-applied change to a live server.

  45. Reconciled a 20‑record DNS zone as code

    Reconciled a 20‑record DNS zone declaratively against the Cloudflare API with separate audit and BIND‑export entry points, and turned the CDN proxy back off on privacy grounds after building it.

    The zone is versioned, comparable and exportable, and the one decision that went against the obvious default is written down with its reasoning so that nobody…

  46. Cut systemd sandbox exposure on every unit

    Cut systemd sandbox exposure across every unit this platform installs — a dead‑man's‑switch service from 9.6 UNSAFE to 1.5, an internet‑facing git forge from 8.3 EXPOSED to 1.5 — and added a converge‑time parser check after finding a misspelled directive silently ignored in three unit templates.

    Every unit runs with the privileges it needs and not the ones it does not, the numbers are measured rather than asserted, and the class of defect where a typo…

  47. 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…

  48. Your code on your own server

    Deployed the company's own git forge on Soft Serve, private by default with no web panel and its SSH port bound to loopback behind a jump host, and made the landing page in front of it a build artefact of the main site rather than a hand‑kept copy.

    The company hosts its own code on its own hardware, and the page in front of it inherits every check the main site passes rather than drifting away from it in…

  49. Ran containers on Podman and Quadlet

    Deployed a container plane on Podman and Quadlet under systemd rather than Docker, because Docker's default bridge‑port publishing can bypass UFW rules — and gave deploys an unprivileged user with one fixed command instead of root.

    Containers run under the supervisor that was already trusted, behind the firewall that was already declared, and a routine release uses one scoped command…

  50. Provisioned a second server from code

    Automated the provisioning of a second server on a second cloud provider, creating the firewall before the machine so it is born behind one, with both providers' firewalls written directly against their REST APIs to avoid a third‑party collection.

    A second host can be created, or re-adopted, from the repository, behind a firewall that already exists, at a cost the file states.

  51. 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…

  52. Split every operational secret per host

    Split the four per‑host operational secrets after establishing that two hosts sharing one dead‑man's switch alert less than two switches, not more, and that a shared backup passphrase can expose both hosts' backups, even in separate repositories, if someone obtains it and can read both repositories' encrypted data and key files.

    Secrets are per host by construction, and the two failure modes that would have followed from sharing them are written down where the next person edits the…

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

  54. A safety net that no longer costs half an hour

    Cut the site's browser‑driven quality gate from 1,636 seconds to 615 by scheduling its checks longest‑first through a worker pool bounded to four lanes, after measuring that alphabetical order cost 320 seconds against 224.

    The gate went from 1,636 seconds to 615, while the checks got broader rather than thinner — the serial cost went up and the wall clock came down.

  55. Replaced 27 font sizes with a 6‑step scale

    Replaced 27 rendered font sizes whose nearest neighbours were 0.6% apart with a six‑step Major Third scale, and wrote the linter that fails the twenty‑eighth.

    Six sizes where there were twenty-seven, with a stated ratio, a stated measure and a check that refuses the next unplanned value.

  56. The accessibility faults your checker misses

    Found and fixed 11 accessibility defects the browser reported as healthy — eight footer links still in tab order behind pointer‑events, a scroll timeline clipping the colophon off three pages, and a rule engine running 70 of its 105 rules.

    Eleven defects fixed and, more usefully, four rules that outlive them: a guard that tests one axis defends one axis, a rule set that does not contain the rule…

  57. Closed the colour system at 28 colours

    Closed the colour system at 28 documented colours with a linter that fails a value painted but undocumented, documented but unpainted, mis‑measured, respelled as a literal, or within a perceptual distance of 0.02 of one already there.

    The palette is a closed, measured set that cannot quietly grow, and the two near-duplicate spellings that prompted it are gone.

  58. Found the light theme missing a whole layer

    Found that the light theme had been missing a full‑page overlay layer since the day it was written, by asserting that both themes paint every layered surface with the same number of layers.

    A layer missing from one theme now fails a commit, and one that had been missing since it was written is painted.

  59. Mirrored the site to Gemini and Gopher

    Built Gemini and Gopher outputs from the same website source; the achievement records 777 documents in each format at that stage, with zero HTML bytes changed by adding the formats.

    Recorded 777 Gemini and 777 Gopher documents in a historical build; zero HTML change concerns adding those output formats.

  60. Replaced 963 metadata blocks with one graph

    Replaced 963 anonymous structured‑data blocks that restated the company 1,671 times with one linked graph of 16 types minted from stable origin identifiers.

    One graph with stable identity replaces 963 anonymous restatements, and the pages carry less rather than more.

  61. Cut the stylesheet bundle from 87 KB to 31 KB

    Cut the stylesheet bundle from 87 KB to 31 KB by taking a base64 font out of it, and dropped 756 KB across 22 files that were published on every deploy and referenced by nothing.

    The bundle is 31 KB instead of 87, 756 KB of dead assets stopped being deployed, and each decision has a measurement attached — including the one that went…

  62. Fixed a sitemap with one shared timestamp

    Fixed a sitemap where 172 of 176 URLs shared one modification timestamp, by taking the date from git history after establishing that the export rewrites every file on every run.

    A re-sync after a month of content edits now touches eight files of 186 instead of all of them, and the sitemap says something true.

  63. Put the documentation under its own linter

    Put the documentation under its own linter — a per‑file line budget that only ratchets down, an index requirement and a real‑path check — which found six of nine plans marked done while carrying unchecked boxes, and fourteen commit‑gating tasks named in no document.

    Twenty-six documents totalling about 2,666 effective lines, each under a budget that cannot grow, with every path and symbol they name checked against the…

  64. Linted the 10,242‑line quality gate itself

    Brought 10,242 lines of quality‑gate JavaScript under a formatter and a linter after establishing it was the largest body of code in the repository and the only one nothing read, fixing 13 findings and suppressing none.

    The largest and most load-bearing code in the repository is now formatted, linted and type-checked, with thirteen findings fixed and zero suppressions.

  65. Built a database‑driven CV generator

    Built a database‑driven CV, references, portfolio and cover‑letter generator in Python — 41 modules, 10,580 lines — rendering six output formats from one 23‑table SQLite source assembled by a 19‑step idempotent pipeline.

    Six formats, three languages and five themes come out of one database, and a corrected sentence is corrected once.

  66. Held the generator to 981 tests and 92% coverage

    Held the generator to 981 test cases at a 92% branch‑coverage floor with warnings treated as failures, and asserted idempotence by running the whole build pipeline twice from an empty file and requiring the second pass to change nothing.

    The pipeline can be re-run against a live database without fear, which is what makes incremental content work possible at all.

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

  68. Enabled every linter rule as an error

    Selected every rule the Python linter has as an error, working through 1,815 findings to reach zero, with each of the few exemptions carrying a written reason and two of them backed by a checker instead of a comment.

    The linter runs at full strength with zero findings, and every deviation is documented at the line where it is taken.

  69. Wrote tests for the checkers themselves

    Wrote tests for the checkers themselves after establishing that a checker fed only clean input will one day report clean because it read nothing — planting a misspelling to confirm the spell‑check finds it, and taking an id range from the database rather than from a number in the test.

    Every checker in the project now has a test that proves it fails on bad input, and the range assertions read from the source of truth.

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

  71. Rehearsed the forge CI hook, found 2 defects

    Rehearsed the forge‑side CI hook and found two defects unreachable by reading the file: a fallback that put an unresolvable argument on the hook's input, and git's own environment variable following the gate into the checkout and turning 19 tests red.

    The hook works on both paths and both defects were found before any real push met them. The limit is that a rehearsal is still a simulation: it proves the…

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

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

  74. Took the test suite to 8.9 seconds

    Took the test suite from six tests over a sixty‑second limit to 135 passing in 8.9 seconds by profiling the main thread and removing the two calls it sat inside for 3,989 samples out of 4,017.

    The suite went from six tests over sixty seconds — 74 seconds of wall clock — to 135 tests passing in 8.9, which puts it inside the window where it runs on…

  75. Named all 17 icons for screen readers

    Named every icon‑only control in the interface for screen readers after finding the send button announced as "arrow up circle, button", and wrote the linter that requires the label within eight lines of the icon.

    All seventeen controls announce their function, and an eighteenth cannot be added without one. The rule's imprecision is real and stated where it is defined:…

  76. Built a 48‑token macOS design system

    Built a 48‑token design system on the platform's own glass material and wrote the linter that rejects a magic number, a hardcoded font size, or an animation that ignores the reduce‑motion preference.

    Forty-eight tokens describe the whole interface, the appearance follows the system, and none of the three erosions can be committed.

  77. Reached the unused half of the core

    Reached the half of the messaging core the application had never used — backup transfer, disappearing messages, message editing and resending, verified invitations, proxies and encryption policy — driving every test against the real library with no mocks.

    The previously unreached half of the core is driven by tests against the real library, and the wrapper carries the highest floor in the project.

  78. Know the licence of everything you ship

    Audited 644 Rust crates for licence compatibility on every build, and proved the check fires by rewriting one crate's licence and by moving the pinned core revision without regenerating.

    The distribution position is checked on every build, and the check is known to work because it was made to fail rather than because it has never spoken.

  79. Built the visual identity from 2 drawings

    Built the company's icon and favicon sets from two hand‑made drawings, with every derived asset regenerated by script and a check that fails when a derived file was committed before its source.

    One drawing now produces every published icon, the tab icon included, regeneration is one command, and a stale asset fails the build.

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

  81. Measured 13 addresses with no tracking

    Measured thirteen addresses from the web server's own access log alone — no cookie, no tracker and no third‑party service — masking the client network as each line is written, and folding the result into a permanent archive of 21 daily counts and 20 monthly facets.

    Thirteen addresses are measured this way, and the site ships no cookie, no tracker and no third-party request, so there is nothing to consent to and nothing…

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