Skip to content
EngineerData
Menu
Design
English

Engineer / Data / 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. 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.

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

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

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

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

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