Zhivko Todorov
ALL CASE STUDIES

CASE 159 · HONEYCOMB · 2025

DEVCONTAINERSCODESPACESDEV ENVPARITY

Dev environments that match production, on the engineer’s first day.

A B2B SaaS company onboarded new engineers with a multi-day "set up your dev environment" experience that produced different states on different laptops. We standardised on devcontainers, ran them through GitHub Codespaces for new hires, and got everyone to parity.

INDUSTRY

B2B SaaS

DOMAIN

PLATFORM

DELIVERED

2025

STACK

DEVCONTAINERS·GITHUB CODESPACES·DOCKER·EKS (DEV)·BACKSTAGE TEMPLATES

RESULTS

What changed, by the numbers.

TIME TO FIRST RUNNING APP

< 30m

NEW HIRE

WORKS-ON-MY-MACHINE TICKETS

−86%

YOY

DEVCONTAINER ADOPTION

100%

ACROSS REPOS

TOOLING-DRIFT INCIDENTS

0

POST-ROLLOUT

HOW IT WENT

The "set up your dev environment" doc was 14 pages and had been updated unevenly across three years. New engineers either followed it carefully (and lost a day) or skipped steps (and produced subtle bugs from missing tooling). Every PR review had a chance of finding "works on my machine" surprises.

Devcontainers per repo encoded the toolchain, the language runtime, the local-dev dependencies. Codespaces ran them in the cloud for the new-hire path — no laptop setup required. Local Docker ran them on existing laptops for the rest of the team. Backstage templates emitted the devcontainer config for new repos automatically.

New hires now ship their first PR within their first day. Works-on-my-machine tickets dropped 86%. Tooling-drift incidents (where some engineers had an older linter version) dropped to zero. The 14-page doc got archived; the README now says "open in Codespaces or run `devcontainer up`."

READY WHEN YOU ARE

Let's get your AWS bill (and architecture) in order.

The discovery call is free. You walk away with at least one concrete idea — even if we never work together.

Or email directly →