21–30 of 36 posts
I also try to write code so small and simple that it approaches the complexity of "Hello World." That way, it's easy to find the bugs.
Comments at the top of the file.
how will you prioritise and track them - open up all the files?
The simplicity and approach of FogBugz is fantastic. Really worth a look if you have the cash to afford it. That being said - they do have provide it for free if you only need 2 accounts. See: http://discuss.joelonsoftware.com/default.asp?biz.5.482288
Trac ( http://trac.edgewall.org/ ) is awesome. It also has very good integration with subversion, if you want that (but you can ignore that aspect if you just want a bug-tracker).
When I have a choice (not very often when working with a company) I use FogBugz. It's a bit pricey compared to FREE, but now that they have a hosted version, it's great if you need to track bugs with a team. The simplicity and approach of FogBugz is fantastic. Really worth a look if you have the cash to afford it. That being said - they do have provide it for free if you only need 2 accounts. See: http://discuss.joel…
Group/open-source projects: JIRA, which was a nice step up from Sourceforge's built-in tracking.
Comments at the top of the file.
On personal projects I use comments like (defun foo (x y z) ;; FIXME: foo should not barf if x is nil and then periodically grep all my sources for "FIXME".