Great intent, but modulating speed is only one of several important vectors toward good code architecture. I would add planning out on paper, in (small) groups

Great intent, but modulating speed is only one of several important vectors toward good code architecture. I would add planning out on paper, in (small) groups. Also, reviewing designs, objects, protocols, schema, etc., before writing code. The author mentions thinking while gardening, but that doesn't share with others. Also, planning for the future, for maintenance, debugability, verification, validation, for re-use, for modularity, for upgraded hardware and in some cases regulatory, etc. And developing documentation before, during and after coding. So yeah, sneaky trick to get us all to talk about our best practices by hyperfocusing on speed :)