A late comment I know but one I just realised is important. This whole article bothered me. And the realisation is that it expects upfront design to work as s

A late comment I know but one I just realised is important. This whole article bothered me. And the realisation is that it expects upfront design to work as something distinct from coding. "The code is the design" (Jack Reeves) is a fundamental point - until you write the code, you are just dealing with "artist's impressions" - vague ideas that might not hang together. The code has to be written (to be thrown away) so that things can be really worked out. Other points: * everyone does not have time to be always commenting on everyone elses iterations. Yes there is time for the big architectural design. But every day? If I am commenting on some other engineers work daily and not actually working with them something is off. * going off and coming back with a big PR. YEs thats bad. Going off and coming back with a Proof Of Concept that will inform the discussion. Thats good. With a Big System, the right way to do it is to do one (at least) to throw away.