Refactoring in Business World... for Developers?
summary
Explains how a team turns refactoring from an occasional task into routine by running inspectoring sessions (initially twice a week), then switching to collaborative code reading sessions where one person reads and the team refactors on the fly, backed by company values that give autonomy and time for Friday experiments. Cites running 50+ refactoring trainings, a two‑year push to embed practices and ~three years to shift company values, and concrete results: more refactors done, higher readability, fewer 3 a.m. wakeups.
AI-written summary · about
chapters (14)
- 0:00Introduction to refactoring
- 3:16From developer to team leader
- 9:47Struggles with hierarchies
- 13:28New project expectations
- 16:46Trap of perfectionism
- 18:12Code reading sessions
- 21:51Trust and healthy conflicts
- 26:55Empowerment and autonomy
- 31:54What motivates developers
- 36:12Why refactor daily
- 38:46Who decides to refactor
- 41:18Teamwork vs micromanagement
- 42:24Company values and trust
- 43:28Q&A
related talks
51mOrganisation Refactoring and Culture Hacking : Lessons from Software
59mManaging Code at Scale
42mRefactoring as an Example of Organizational Change
01h 00mDev Culture Hacking and Org Refactoring Transformation tips from Software Pros
31mMakeover Monday 💅✨: How a Weekly Ritual Transformed...
49mHow to sell a big refactor or rewrite to the business?
42mHow to sell a big refactor or rewrite to the business?
51mFrom Developer Pain to Impact: Establishing Large Scale Refactoring at SAP