(15 February, 2002) Your bugs, design flaws, and security holes could cost your customers billions of dollars.
(25 January, 2002) here I'll give you my reasons for writing automated tests. You can decide whether or not it is right for you. (My way is of course right, but I'll let you decide whether you want to write software the right way or the wrong way.)
(15 January, 2002) Since it's the lowest-level logging that gets used and all the messages coming into it get logged into a file, I made the code very verbose when it gets errors. I did this because there's no lower level to complain to. I also did it because, hey, if you're calling the logging component, you've already encountered an error condition -- my code does not return errors.
(4 January, 2002) This is the story of how I added yet another bit to yet another register in the Gospel According to Brian.
(31 May, 2001) One of the best ways to improve the quality of your software is also possibly at the same time the most overlooked and the most effective use of your time.
(1 Mar, 2001) I moved last month, and during the move I had some useful tools packed away in the truck. You never realize how much better a drill is versus a screwdriver until you try to hang blinds into old wood with about fifty layers of paint..
(29 Mar, 2002) If you're just going to stick a function prototype into the C file to stifle warnings, you might as well drop the warning level on your compiler to the point where it stops complaining about missing prototypes.
If the preceding paragraph describes you and are attempting to write C++, I'd suggest sticking to straight C. If you're going to shoot yourself in the foot, you might as make a nice, clean hole just behind the toes (C) rather than blowing your leg off from the knee down (C++).