The Duct Tape Programmer

Post by tszming » Sun, Oct 10, 2010, 7:12 AM UTC

hello_moto wrote: post #15

qw wrote: post #8

I have a similar feeling towards TDD. I use test driven developments for those parts of my code that needs it. I recently had to create a function that did some complex calculation. TDD was great for that, because I had a set of known inputs and a set of known outputs. It made sense to write the test before the code. But I will not write trivial tests just to make the unit test coverage increase. I've seen tests writ…

I agree with you about getter/setter and trivial code. But sometime when you're a VP of Engineering and you knew that most of your developers will slack off eventually and start not writing unit-test guess what you'll do? You set the code coverage bar high enough. While I disagree with the said VP or Lead or Senior people, but sometime we have to admit that not many developers in our industry care about quality and h…

Post by hello_moto » Mon, Oct 11, 2010, 1:02 AM UTC

tszming wrote: post #41

hello_moto wrote: post #15

Earlier quoted context omitted.

I agree with you about getter/setter and trivial code. But sometime when you're a VP of Engineering and you knew that most of your developers will slack off eventually and start not writing unit-test guess what you'll do? You set the code coverage bar high enough. While I disagree with the said VP or Lead or Senior people, but sometime we have to admit that not many developers in our industry care about quality and h…

Feature, Quality, Time - as a VP of engineering, you need to pick two of them.