Re:Is TDD Worth It?
by trothoun on Saturday September 28, 2013 @09:39AM
(#6461776)
sometimes you can't even really express what the problem is, until you've taken a stab a solving it. The problem might be something like 'This feature is awkward and doesn't feel quite right.' When I'm doing exploratory coding, I need to be able to feel my way through a problem. I have yet to learn to do that from the vantage of tests, and am somewhat skeptical that I ever will.
[ Parent
| on HN ]
Re:Is TDD Worth It?
by RougeFemme on Saturday September 28, 2013 @05:29PM
(#6463215)
You can't really express it, but you still have an idea of what the problem is. . ."solving it". . .you have an "it" in your mind. Also, in many cases, when you are working on a "less technical" feature, there are others who can help express what the problem is. . .user, designer, architect, etc. It's often really tough for a developer to express what the problem is in a vacuum.