Friday, May 30, 2008

Commits

I'm happy to see the first sets of commits coming in from our SoC students this year, and I just wanted to take a moment to remind everyone of two things:

1. Commit early, commit often. You should be committing once per (working) day, minimum; more often is better. Use the source control tools to your advantage. If it builds, check it in, with appropriate comments. It's just like making sure you hit the save button every once in a while, but better...you can always go back to older versions. Nobody is going to criticize you for committing a work-in-progress (and you might get some good ideas from people who review commits as they come in).

2. If it hasn't been committed, it doesn't exist. If you want to talk to someone about your code, it's best and easiest if it's in the repository. Likewise, if your mentor is evaluating your status, they're not going to go off of what may or may not be on your hard drive, they're going to go off of what they have access to.