Something I'm bad at

I've re-discovered something I am bad at. I'm slightly ashamed to admit it, but I am very bad at testing my own code. To be specific, I'm bad at spotting when fixing one problem causes or re-introduces a different one. I already know the fix for this. It is quite simple: write the unit tests as you go along, and make sure they all still pass after you've added a new bit. I let myself slip away from doing this, because I was feeling some deadline pressure. But I just proved to myself yet again that writing tests doesn't cost you time, it saves you time.

Well, lesson learned — properly this time, I hope.

Tag:

Comments:

Chris, Timely commentary! It appears that GNOME 2.12 initiates far less (25%) system resources (memory) compared to KDE offerings. Interesting to note where a 'skipping' audio disk issue leads one. Testing remains IMPORTANT AS ALWAYS!

Posted by William R. Walling on October 20, 2005 at 01:13 PM PDT #

Code reviews are another useful tool which is often overlooked.

Posted by Chris Quenelle on October 23, 2005 at 01:09 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

terryh

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today