Does "measure twice, cut once" have an equivalent in software design?
Something like "Spec it out twice, code it once"
Thread
Login to reply
Replies ()
What about "Throw shit at the wall and see what sticks"
Spec it out thrice, review the code twice and stop once freedom tech prevails
Prompt it thrice, see if it's nice?
Plan to throw one (implementation) away; you will, anyhow.
-- Fred Brooks
yes, I think this is it!