DISQUS

Kevin Pang · 1 year ago

That was very well written. It's rare these days to see bloggers take the time and due diligence to write up something like this. Thank you for the interesting read.

I find that your experience with TDD to be very similar to mine -- a little slow at first, but without a doubt worthwhile. I'm not so sure I agree with the analogy of TDD being the fingers of a potter; I think the comparison works better to software development as a whole. I'm not actually sure where TDD fits into that analogy to be honest. Perhaps that's why it's so hard for some to adopt it. There are very few professions where something like TDD is encouraged, so it only makes sense that it feels a bit unnatural to developers (and even moreso to newer developers who have not had to experience the pain that comes from working with code that is not unit tested).

Anyways, those are my thoughts. Thanks again for the great read. :-)

nstults · 1 year ago

I appreciate the compliment. I agree, my analogy was just one aspect of TDD, whereas it is a much larger practice than that. It's a strange practice - it is has immense value, and I agree that part of its difficulty is the lack of any counterpart in usual experience. It goes against the natural grain of logic - how can you test something you have only vaguely conceived? But you should. One of the things I love about software development, though, is its uniqueness - software as a medium is so pliable, so flexible, that it defies the usual approaches to engineering, which is why I think people have started calling it a "craft" - but it's also engineering - hard to pin down :) Thanks for the comment, and I'm glad you appreciated the post.