Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 1
    I can't emphasize enough how important the points you've made about prototyping are. I don't think this is really what the question was about (mainly about when it's ok to stop and design, rather than just build as I understand it), but prototyping is definitely a relevant part of that process. Nice job! Commented Jun 7, 2013 at 13:10
  • 3
    I'm quite puzzled as to why I'd get a downvote here. Please be kind enough to give information on that, so I can see the errors of my ways, sensei. Commented Jun 7, 2013 at 15:58
  • 1
    Have reassigned this as the answer because it covers more relevant scenarios Commented Jul 24, 2013 at 17:23
  • 7
    I used to work with a mechanical engineer who put it like this: Do you want your product under-engineered or over-engineered? These are really the only two options. Commented Aug 14, 2013 at 22:25
  • 1
    @SamtheBrand: thanks for the great edit. Much better. Commented Jan 18, 2014 at 13:50