Some day, somewhere in the net there was iBlog. It was about everything and nothing. A few persons was reading it, some of them maybe even liked it. But I am not interested in writing about myself anymore. This blog will be about Project Management. Less personal, but in fact it will be my personal tool: to not forget what I have learnt. And what I ll learn in future.
Blog > Komentarze do wpisu

Untested code

Untested code is broken code”
— Philipp von Weitershausen, Martin Aspeli
sobota, 05 kwietnia 2008, d_l_x

Polecane wpisy

  • Two management styles

    Management styles might be divided, at least for my own purpose, into two basic categories. The first category is black/white style. A black/white manager usual

  • Avoiding large penalty for a late change.

    One way to avoid the large penalty for a change during final production is to make the right design decision in the first place and avoid the need to change lat

  • Performance Rating of a Manager

    Performance rating of a manager cannot be higher than the one we would accord to his organization [he manages]. Andy Groove, High Output Management

Komentarze
Gość: , *.chello.pl
2008/04/06 22:20:55
Some bullshit - how does he know that it is broken if he hasn't tested it?
-
2008/04/10 20:42:26
Bullshit? Have you ever written a code which worked just after writing, in the first run :)?
-
Gość: , *.chello.pl
2008/04/14 13:57:07
That is beside the point. The point is: the untested code is in an unknown state - you just don't know whether it is broken or not. Assuming either way is not correct.

And for teh record - answer to your question is "YES" (I am THAT awesome :)