Your Job Sucks and This Is Why
summary
A case study of integrating two companies compares a Spotify-style org (no middle managers) where engineers run Jenkins pipelines, own incidents, can rollback in three minutes, and track explicit per-test metrics (unit, snapshot, e2e, performance, stability, localization, SEO). It shows business figures tied to technical choices (an $18M debate leading to an IE10 decision) and finds that only 35% of engineering time went to new features while ops, security, compliance, and cultural mismatch — not technology — caused most integration failures.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:00What is culture
- 7:26Engineering culture
- 11:07Integrating teams
- 13:19Spotify model impact
- 16:11Culture differences
- 21:32Autonomy and open source
- 24:04Engineer as king
- 27:41Understanding engineering culture
- 34:24Corporate culture origins
- 41:52Q&A
related talks
05m5 ways to burnout your engineers
38mThe Human Element in Development
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
01h 01mBecoming an Engineering Manager Without Losing Your Technical Soul
39mRemoving Barriers
25mEgoless Engineering
05mHow to Destroy a DevOps Engineer
18m"Hoodwinked by the Terrible Trivium"