Shipping Quality Software In Hostile Environments

A 10GB monorepo. An hour-long deployment. See how a small team secretly dismantled their broken system from the inside.

#1about 4 minutes

Defining hostile environments and technical debt

Technical debt is the implied cost of easy solutions, manifesting as unpaginated APIs, fragile code, and broken deployment processes.

#2about 6 minutes

The compounding harm of ignoring technical debt

Common excuses for tech debt lead to a vicious cycle of lower productivity, tanking morale, and a "bad neighborhood" codebase where quality standards are abandoned.

#3about 7 minutes

A case study of a company in tech bankruptcy

A real-world example shows how a monolithic repo, on-premise tooling, and a lack of local development environments led to daily outages and technical bankruptcy.

#4about 6 minutes

How a small team fixed tech bankruptcy incrementally

A small ops team worked "in the shadows" to incrementally rebuild the build server, split the monorepo, and automate deployments using Ansible.

#5about 4 minutes

Rebranding tech debt as ongoing sustainability work

Shift the mindset from "paying down tech debt" to "sustainability work," treating it as regular hygiene necessary to maintain development velocity.

#6about 10 minutes

Gaining management buy-in for sustainability work

To convince leadership, avoid all-or-nothing projects, deliver small valuable increments, and frame the work as essential for maintaining long-term productivity.

#7about 3 minutes

Why everyone in the company should care about sustainability

Sustainable development is a shared responsibility from the CEO to junior engineers, as it ensures the company can continue to deliver results efficiently.

#8about 2 minutes