Zero-defects code: the prescient Microsoft memo from 1989

21 days ago

Microsoft's 1989 Zero Defects memo advocated for principles like continuous integration and test-driven development long before they became mainstream.
The memo highlighted problems in Microsoft's culture, such as rewarding developers for checking in incomplete code and treating schedules as more important than quality.
Chris Mason argued that writing perfect, zero-defects code was achievable and emphasized the need for a mindset shift to prioritize quality over speed.
Key solutions proposed included having a working, shippable product daily, fixing bugs immediately, and shifting testing to quality assurance rather than bug-finding.
The memo suggested practical techniques like code reviews, writing tests before debugging, and using asserts to verify assumptions, aiming to reduce bugs and improve predictability.
Leadership committed to supporting realistic schedules and pushing back against pressures to cut corners, emphasizing that taking minor heat early was better than major issues later.

Hasty Briefsbeta