This reminds me of https://twitter.com/marick/status/787402452848873472 https://twitter.com/marick/status/787402452848873472 I dont think writing Tests first m

This reminds me of https://twitter.com/marick/status/787402452848873472 https://twitter.com/marick/status/787402452848873472 I dont think writing Tests first makes you work top down or bottom up. If you want to work bottom-up (I like to work bottom up) you just start by writing tests for your bottom up functionality. And of course I don't want to impose TDD on others, but I would like others to try it out sincerely (recommending kent Becks book for this. Don't do it without guidance, many people who reject TDD after trying it out were doing some kind of Test-first method, but didn't get the benefit because they were not aware of stuff like get one test at a time to complete, etc.) --------- > shouldn't be taken as dogma. Life in software engineering becomes much more relaxed when you realize that every piece of advice and technology is in fact based on dogmas and is not based on sound empirical, statistically relevant evidence :-) (apart from the pure math part). It is just really really hard to study software quality in an objective way that satisfies scientific criteria. So we are kind of stuck with hearsay in IT So TDD is kind of dogmatic. So is OOP, or the rejection of gotos.