A client's staging environment had drifted so far from production that developers stopped using it. Tests passed in staging and failed in prod. Tests failed in staging and passed in prod. Eventually the team just stopped looking.
- Published On
devops
- A consulting engagement where we finally opened the cloud bill and found forgotten dev environments, runaway log storage, and a data pipeline reprocessing everything from scratch every night.
- Published On
- A 47-minute build pipeline had become sacred infrastructure. When we finally opened it up, we found cargo-culted steps, redundant checks, and a team afraid of their own tooling.
- Published On
- We built a canary deployment pipeline with automated rollbacks. It still let a bad release through to 100% of users. Here's what went wrong.
- Published On
Tags
consulting (29)developer-experience (14)architecture (9)reliability (7)debugging (6)devops (4)performance (4)observability (4)code-quality (4)ai (4)database (3)microservices (3)testing (3)engineering-culture (3)technical-debt (2)productivity (2)ci-cd (2)tooling (2)javascript (2)postgres (2)goals (2)environments (1)queues (1)cloud (1)cost-optimization (1)postgresql (1)orm (1)refactoring (1)on-call (1)alerting (1)incident-management (1)typescript (1)kubernetes (1)distributed-systems (1)caching (1)platform-engineering (1)security (1)dependencies (1)deployment (1)code-review (1)feature-flags (1)api (1)contracts (1)logging (1)mongodb (1)migration (1)workflow (1)nestjs (1)angular (1)sandbox (1)sonarcube (1)learning (1)journey (1)mdx (1)