Best Practices / Tools for programming

What are yours?

[Clark]

I was just thinking, these days I take longer and longer to develop code because I keep wanting to add things and it just becomes an unmanageable beast. It dawned on me that if I started using a version control system, even though I'm the only one working on my code, as well as using the same system to manage bug reports and requested features, I'd stop trying to put every feature into what I'm doing, prioritize better and be more organized. Problem is, never used a version control system (other than Microsoft Project, which isn't really). Is there any reasonable priced system that helps you with your coding projects?

Part 2, what are your best practices / tools for coding your projects?

[mford]

The more you delay projects the more chance there is of someone else cutting into your space or change the space for where your ideas live. I have seen new business operating models completely wipe out all the work one invests in development simply because they were over ambitious or poorly managed.

If you let a project drag on without positive feedback in a reasonable time, you stand the chance of losing direction and enthusiasm.

Keep your "big picture" but keep short term realisable goals; aim to hit 80% - 90% then go live; think evolution more than revolution.

One of the biggest problems with programming is the way it can suck you in, taking you on all sorts of tangents. You can manage on todo lists but you have to strictly recognise the difference between must-do's and would-be-nice-to-do's.

More thoughts on the subject anyone?