Preferring throwaway code over design docs
published on 2024/12/16
This approach dovetails with show don’t tell. A prototype can be worth 1000 design docs. If you want to drive change, you don’t usually do it in docs, but in code. Yet with an undisciplined organization you run the risk of your prototype being seen as the answer, not the question. The org may assume it says “we should do this!” When it really should be “should we do this? Or some other thing?”
[softwaredoug](https://softwaredoug.com/blog/2024/12/14/throwaway-prs-not-design-docs(
We agree with this. Design document and prototyping iterations come hand to hand.