The new year is a popular Schelling point to make changes to your activities, habits, and/or thought processes. This is often done via the New Year's Resolution. One standard piece of advice for NYRs is to make them achievable, since they are often too ambitious and people end up giving up and potentially falling victim to the what-the-hell effect.
Wikipedia has a nice list of popular NYRs. For ideas from other LW contributors, here are some previous NYRs discussed on LW:
- Somervta aimed to spend at least two hours/week learning to program (here)
- ArisKatsaris aimed to tithe to charity (here)
- Swimmer963 aimed to experiment more with relationships (here)
- RichardKennaway aimed to not die (here)
- orthonormal aimed (for many years in a row) to make new mistakes (here)
- Perplexed aimed to avoid making karma micromanagement postmortems (here)
- Yvain aimed to check whether there was a donation matching opportunity the next week before making a donation (here)
(If one of these were from you, perhaps you'd like to discuss whether they were successful or not?)
In the spirit of collaboration, I propose that we discuss any NYRs we have made or are thinking of making for 2015 in this thread.
Personally it sems that number of commits is a metric too easy to game. If you generally are honest with yourself, keep it, but I wouldn't use it if I were to set a goal for a group of students. Another metric that is less easy to game on a personal level is time spent with your programming environment open, which is effective if you tend to either not start programming or stop prematurely. Finally the ideal metric is to have a set of features or a certain output you want to achieve and have that as a goal with the caveat that these goals tend to be too hard to achieve in the mean time.
So overall, I'd recommend time spent programming as a weekly goal and a final product as an overarching goal with the explicit option of re-negotiation.