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.
It's a great idea. The most important part (possibly the only important part) of learning to code is to actually write code, code that's useful to you. Small commits are a good habit (too many people have an SVN-era instinct that commits are "expensive"). Heck, if I were doing this (as someone with a full-time job that's mostly coding) I'd make it a branch every day, with at least 8 commits on it. (Perhaps if you want to follow CBHacking's suggestion you could make it a branch every week, with at least 7 commits on it; that way, to be "on target" you commit every day, but you can miss a few days and make it up if you need to).
My standard way to avoid the "what the hell effect" is: miss one and it's ok, miss two and it's all over.