Finding bugs: I'm a big believer in Linus' law - which basically says that the more people look at your code, the more likely you are to identify bugs. In my e

Finding bugs: I'm a big believer in Linus' law - which basically says that the more people look at your code, the more likely you are to identify bugs. In my experience, the single best way to identify bugs and other problems is to have a good code review process. Any at all is better than none. Code review can be frightening for the person whose code is being picked apart, but it is important to remember that it shouldn't be a personal thing. Even the best developers in the world write bugs - it's just the nature of the beast. If you don't have a continuous integration process, think seriously about implementing one. It can be a pain in the arse to set up continuous integration after a project is already well under way, but do it anyway - because it will most likely save you a ton of time further down the road.