Makeover Monday 💅✨: How a Weekly Ritual Transformed...
summary
A weekly, developers-only ritual that runs as a 60‑minute Monday (later 30‑minute) session uses GitHub‑labeled issues + project board or a Jira swimlane to track refactors, runs six‑minute sticky‑note brainstorms, and pairs work after the meeting. On small teams it doubles understandability; on an 8.5‑year codebase with ~140 contributors and ~50 active contributors it surfaces priorities and spawns cross‑team effort. SonarQube integrations find concrete issues; outcomes are cleaner code, faster onboarding, and shared standards. Try the method‑rename exercise: comment then rename.
AI-written summary · about
chapters (19)
- 0:00Welcome
- 1:08Beauty in code
- 3:14What is refactoring
- 3:56First team launch
- 6:25Makeover Monday meetings
- 8:11First team improvements
- 9:36Legacy codebase move
- 11:04Proposing refactoring
- 12:29Second team Makeover
- 14:14Second team changes
- 15:59Beyond one team
- 17:06Cross-team refactoring
- 19:39Refactoring priorities
- 21:22Readability ROI
- 23:53Year in review
- 25:21Blueprint for ritual
- 28:36Practical exercise
- 30:01Refactoring and AI
- 30:46Closing
related talks
45mRefactoring in Business World... for Developers?
46mCracking the cadence of your software engineering 1:1s
06mHow Sonar Builds a Culture of Innovation and Accountability
01h 00mHow microteams change the way we collaborate
41mThe Life Changing Magic of Tidying Your Dev Team
18mCan I change my organisation?
31mHarmonizing Across Product & Engineering (Cross Team Collab)
23mManaging diverse engineers for high-impact deliveries