4 ms·
This makes me wonder even more though when you put it together with this part of your post: ...I have good hope that in the long run this will tremendously inc
by mattmanser 15y ago
This makes me wonder even more though when you put it together with this part of your post:
...I have good hope that in the long run this will tremendously increase my productivity. Even if in the short term it seemed as though my productivity took a hit (after all, writing code that tests stuff does not add any functionality to the program itself).
You seem to be saying that even though you've been doing it for a year, you're still suffering a drop in productivity. Have I misunderstood you? Doesn't that indicate that it's actually not a good idea? Or do you have evidence that there's less customer visible bugs to deal with? (evidence rather than your hopes would be better :)
It doesn't really feel like you've communicated why all that extra testing code is so great. And let's not forget that's what it actually is, code which can be wrong itself. And you're not even doing TDD but adding them way down the line!
- jacquesm 15y agoThere definitely is a drop in initial productivity, after the exploratory phase is over there is a hick-up in the output because I'm writing test cases. Then, as soon as that is done there is a huge boost in productivity because it becomes much (and I can't emphasize enough how much that really is) easier. So it is more a matter of uneven output than an overall loss, overall it is definitely a net gain. Hard to quantify though because you will never know how much time you would have spent debugging and testing if you had not written those tests first. It is more of a feeling than that it is measurably slower, in fact it is measurably faster but when writing the test cases it feels slower. I hope that clears it up, sorry for the confusion! As for fewer customer visible bugs: yes, absolutely, no doubt about that.