Apr. 23rd, 2010
unittests and you, the developer
Apr. 23rd, 2010 05:00 pmSo you think that's managers fault that you do not use unittests in your code.
Interesting. Are they also guilty that you have ugly names for methods and variables? That your method takes 100+ lines? Is it managers fault that your classes lack any kind of design, and your code is tasteless?
See what I mean. If you do not have unittests for your code, it is your own fault.
That's it for Friday; I have run my tests, submitted my code and the binary, updated the wiki regarding latest api changes, and even wrote the weekly status right now, instead of Monday morning.
It is 4:59 Friday, and I'm going home, to play golf, then have dinner, then play canasta. Weird, eh?
Interesting. Are they also guilty that you have ugly names for methods and variables? That your method takes 100+ lines? Is it managers fault that your classes lack any kind of design, and your code is tasteless?
See what I mean. If you do not have unittests for your code, it is your own fault.
That's it for Friday; I have run my tests, submitted my code and the binary, updated the wiki regarding latest api changes, and even wrote the weekly status right now, instead of Monday morning.
It is 4:59 Friday, and I'm going home, to play golf, then have dinner, then play canasta. Weird, eh?