Skip to content
Engineer
Menu
Design
English

Engineer / Services

Shipping changes without drama

Tested, released and reversible, so changes reach customers on a Tuesday afternoon rather than late on a Friday night.

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

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

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

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

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

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

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

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

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

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

  11. Infrastructure simplified beyond AWS

    Reworked an international client’s infrastructure by removing unused services, adjusting capacity and moving workloads away from AWS. The founder reports a 10x reduction in cloud costs with no loss of productivity.

    Reviewed an international client’s infrastructure, removed unused services, adjusted capacity and moved workloads away from AWS.

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

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

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

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

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

  17. Built the entire core infrastructure from scratch

    As one of the first hires, designed and built the entire core infrastructure and supporting processes from scratch for a green‑energy SaaS startup, laying the foundation for rapid growth.

    As one of the first hires, designed and built a green-energy SaaS startup's entire core infrastructure from scratch, enabling rapid growth.

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

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

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

  21. Built first‑party error monitoring and tracing

    Built first‑party error monitoring and OpenTelemetry tracing rather than buying them — payload sanitising, spike and regression detection, symbolication and a synthetic heartbeat — behind 11 operator views.

    Built first-party error monitoring and OpenTelemetry tracing — sanitising, spike detection, symbolication and a heartbeat — behind 11 operator views.

  22. 1,022 migrations behind a schema drift gate

    Kept the schema honest across 1,022 migrations with a CI gate that builds the database both ways — a fresh install, and an install plus every migration — and fails when the two disagree.

    Kept the schema honest across 1,022 migrations with a CI gate that builds the database both ways and fails when the two disagree.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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