
Designing it twice

The Philosophy of Software Design – with John Ousterhout
Topic 6 of 15
Published Apr 9, 2025 · Clip 20:02–26:38 (6:36)
John explains how brilliant students develop bad habits because everything was always easy for them, so their first ideas were always good enough. He forces students to consider a second approach, and the second idea is always better. His best career example: designing the Tk toolkit API on a long plane ride with two designs, choosing the second—one of his best professional ideas. He notes design-it-twice costs only 1-2% of total project time, and that design always involves tradeoffs that good designers learn to balance through experience.