Does "measure twice, cut once" have an equivalent in software design?
Something like "Spec it out twice, code it once"
What about "Throw shit at the wall and see what sticks"
Please Login to reply.
No replies yet.
