kinar wrote:

75-90% of the code I write will never see production and would just clutter a source control system.

Wow. My workflow is the exact opposite of this. I rarely write code that isn't intended for production and I check in my changes several times a day; sometimes as often as every fifteen to twenty minutes. This fits very well with the nature of the software I write. The place I work is so small we don't have a formal QA process so most of that burden is on the developers' shoulders. So I rely heavily on automated testing. A full suite of well written unit tests goes a long way toward ensuring the code I write does what its supposed to. The way projects are divided, I don't have to worry too much about troubleshooting someone else's code. Its pretty much one programmer per project with interaction only when projects need to interface with each other. I've automated the build for my project and it runs an incremental build after each check in. Unit tests are run as part of the build process, while system and integration tests are run on a series of virtual machines for different scenarios that are reset before each run. The other developers each have their own methods but mine works quite well with my development style.