Last week I made the case for codebase transparency: why 21st-century dev leaders need real-time insight into the strengths and weaknesses of their codebase, and why new quality metrics are going to be the principal solution. This week, I want to look at how this actually works in the day-to-day progress of a company.
Case study 1: the regular meeting
It’s the first Wednesday of the month, and your dev team leads step away from the gentle hum of CPUs and caffeinated frontal lobes to gather in the meeting room, lattes and laptops in hand.