Quote:
Originally Posted by clowntable
Well once you start to change stuff and need to see if other things break or once components get combined I'd rather have the test
I don't know either way right now, but I believe that only using wishful thinking is really bad. Why would I want to clutter up my code with danglers when it does nothing to help me achieve the end result? I think that focusing on the separation of the code base is a better approach, ie, you build each section as a stand-alone proto-primitive that you can later combine.
I dare say it: too much wishful thinking can lead to premature optimization.
The wishful thinking is really one little concept they offer up at the beginning of the course. Yeah, the ideas build on a notion of wishful thinking, but focusing on the short-comings of wishful thinking is sort of like using assert statements to describe the entirety of a TDD book, then calling into question all of TDD because assert statements aren't really effective.