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.
-
Avoiding Java memory layout pitfalls with examples and funky tools
-
Sauce Labs Appium Now Can Test Android and Firefox OS Apps
-
DEMUX Framework
-
Protect yourself from the coming cloud crack-up
-
Automatically build and include one Eclipse project into another as a JAR file
-
WinJS observables (Part III) - using WinJS.Binding.define
Add your comment
