Continuing on the theme of building game mechanics into our projects... couldn't we do this if we wanted to?
Post-deploy hooks are available for your source control system of choice. You could have your computer tell you "Nice job" for one commit (if automated tests pass), "Keep it going!" for two in an interval, "He's on fire!" for three, "BOOM that's amazing!" for four, etc etc. This would incentivize yourself to do "just one more commit", in the same fashion as Civ and whatever get "just one more turn."
(If doing it over a work day wasn't working for you, you could bump the visualization to your dashboard and create a chain, with one link for every day you do task X. Don't break the chain, as per Seinfeld.)
This assumes, critically, that a commit is a measure of forward progress towards business goals.
Post-deploy hooks are available for your source control system of choice. You could have your computer tell you "Nice job" for one commit (if automated tests pass), "Keep it going!" for two in an interval, "He's on fire!" for three, "BOOM that's amazing!" for four, etc etc. This would incentivize yourself to do "just one more commit", in the same fashion as Civ and whatever get "just one more turn."
(If doing it over a work day wasn't working for you, you could bump the visualization to your dashboard and create a chain, with one link for every day you do task X. Don't break the chain, as per Seinfeld.)
This assumes, critically, that a commit is a measure of forward progress towards business goals.