Hacking Development Culture: Treating Developers As People

on YouTube ↗29m

" summary

Company upgrades a Rails 2 monolith while still shipping features, running against 12 billion records and 18 million visits a month. A 184‑line SEO controller gets refactored into service objects so actions are ~6 lines, tests and routing specs become simple, and the baseline rises to 70% test coverage. Team introduces code review, pair programming, TDD, encourages side projects, adopts Angular after a spike, and moves an app to RDS; the migration and culture shift take about a year and a half and cut bugs and maintenance time.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 2:19Spokeo and its scale
3. 6:05Technical debt at Spokeo
4. 11:08Single developer growth
5. 14:21Fixing debt and patterns
6. 19:45Refactoring with service objects
7. 22:36Balancing expectations
8. 24:01Democratic dev decisions
9. 25:53Side projects and spikes
10. 26:36Investing in engineers
11. 27:42Cultural change hurdles

" related talks

• 34mBuilding a Culture of LearningJoe Mastey · MountainWest RubyConf 2015
• 35mRewriting Code And CultureSabrina Leandro · RubyConf Portugal 2015
• 35mA Tale of Two CodebasesPat Maddox · MountainWest RubyConf 2010
• 26mHow to be an Awesome Junior DeveloperEric Stiens · Nickel City Ruby 2014
• 30mThe Elements of ScalingCamille Fournier · The Lead Developer New York 2017
• 59mTech leadership, one year afterJoão Alves · Software Crafters Barcelona 2019
• 34mShitlist-driven development and other tricks for working on large codebasesFlorian Weingarten · RedDotRubyConf 2017
• 36mRebooting CultureCamille Fournier · The Lead Developer 2016