I'm currently working on K-Pad v1.1.2. I'd hoped to stick with v1.1.1 for a while, and concentrate on my other work, but another ugly code bug reared its head. So, as a bit of light-hearted relief while I await another 20 min recompile, I thought I'd list here those times that my software gets bugs.
1. When I think I've finally produced a bug-free version;
2. When I've just gone to the effort of compiling, and releasing a new version;
3. After I've decided (on a whim) to change the tiniest detail (usually for cosmetic reasons);
4. The instant I've bragged to somebody (or myself) how good a programmer I think I am;
5. When my own meta language has evolved (tree.size () , for example: two years ago I may have thought that the size was the number of open branches; now, the total number of branches);
6. When I assume something, especially if it's "Oh, I don't need to test that (again)";
7. When I'm changing 200 entries at speed, and forgetting that (unfortunately, annoyingly) the context can be important;
8. When I'm showing off my prog to someone else!
By far the quickest way to discover bugs is 8. above. That's why I need beta-testers!! ;-)
K-Pad is a multi-featured notepad / organizer for Windows: print-out pages or booklets of photos, tables, and rich text.More... | |
This is my support blog, featuring help, tutorials, and comment. Welcome. :-) |
Tuesday, 26 August 2008
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment