←back to thread

388 points replyifuagree | 1 comments | | HN request time: 0.248s | source
Show context
paulsutter ◴[] No.37965627[source]
The only magic wand in software development is to simplify requirements. The requirements are always wrong: too broad, too vague, based on invalid assumptions

The real genius is to propose a simplified solution, by discarding some assumptions. This is the best and only way to shrink the schedule

replies(7): >>37965809 #>>37966142 #>>37966325 #>>37966429 #>>37966768 #>>37966963 #>>37967034 #
1. marginalia_nu ◴[] No.37966768[source]
Yes. I very much agree. Not only are most software bugs actually requirements bugs, the speed you can build software with good requirements is absolutely bonkers.

I've seen a project go from an empty repo to production in two months with a set of requirements that were completely unambiguous and rock solid. I've also seen ambiguous and vacillating requirements drag out the implementation a ~30 LOC feature for months.