By hendrikbeck
via blog.hendrikbeck.com
Published: Jan 17 2013 / 10:44
The basic idea behind Hypothesis-Driven Development is simple: you formulate assumptions, or hypotheses, instead of requirements and you determine signals, that will help you find out whether you were right or wrong. Where test-driven development et. al. help you build your product right, this is an approach that guides you to build the right product.
-
Prepare your SharePoint 2013 farm for App development and debugging
-
How Vidmind Started Their Move From Java to Scala, Part One
-
html-inspector · GitHub
-
animate.css, animation by toggling css classes | Coders Grid
-
5 Reasons for Building Tactical Services
-
Using PostSharp to Add ServiceStack Route Attributes
Add your comment
