candera · November 16, 2011 14:57 · Dec 27, 2011 · Dec 27, 2011 · Dec 24, 2011 · Nov 16, 2011
diff --git a/hundred-day-hacking.md b/hundred-day-hacking.md
@@ -11,6 +11,7 @@ A friend of mine, as a way to "level-up" her young daughter at violin, set a goa
 ## The Rules
 
 **Update:** I changed the rules to allow issue activity as well.
+
 **Update:** I changed the penalty for missing days.
 
 Every day, for 100 days in a row, create a new event somewhere on GitHub. It can be of any size, on any project and can include commits or updates to issues. If you miss one day, lose two points. If you miss a second consecutive day, lose four additional points. Double the penalty for each consecutive day: four consecutive days would total 30 points lost - 2 + 4 + 8 + 16. Your score cannot go below zero.

diff --git a/hundred-day-hacking.md b/hundred-day-hacking.md
@@ -10,8 +10,9 @@ A friend of mine, as a way to "level-up" her young daughter at violin, set a goa
 
 ## The Rules
 
+**Update:** I changed the rules to allow issue activity as well.
 **Update:** I changed the penalty for missing days.
 
-Every day, for 100 days in a row, create a new commit somewhere on GitHub. It can be of any size, on any project. If you miss one day, lose two points. If you miss a second consecutive day, lose four additional points. Double the penalty for each consecutive day: four consecutive days would total 30 points lost - 2 + 4 + 8 + 16. Your score cannot go below zero.
+Every day, for 100 days in a row, create a new event somewhere on GitHub. It can be of any size, on any project and can include commits or updates to issues. If you miss one day, lose two points. If you miss a second consecutive day, lose four additional points. Double the penalty for each consecutive day: four consecutive days would total 30 points lost - 2 + 4 + 8 + 16. Your score cannot go below zero.
 
-Note that this *includes* changes to a wiki. It's not cheating because GitHub wikis are themselves git repos. Including wiki work gives you a way to have days where the work you did was primarily thinking, not typing, but it still makes you write down at least some of what you thought about.
+Note that commits *include* changes to a wiki. It's not cheating because GitHub wikis are themselves git repos. Including wiki work gives you a way to have days where the work you did was primarily thinking, not typing, but it still makes you write down at least some of what you thought about.
diff --git a/hundred-day-hacking.md b/hundred-day-hacking.md
@@ -10,6 +10,8 @@ A friend of mine, as a way to "level-up" her young daughter at violin, set a goa
 
 ## The Rules
 
-Every day, for 100 days in a row, create a new commit somewhere on GitHub. It can be of any size, on any project. If you miss a day, start the count over. 
+**Update:** I changed the penalty for missing days.
+
+Every day, for 100 days in a row, create a new commit somewhere on GitHub. It can be of any size, on any project. If you miss one day, lose two points. If you miss a second consecutive day, lose four additional points. Double the penalty for each consecutive day: four consecutive days would total 30 points lost - 2 + 4 + 8 + 16. Your score cannot go below zero.
 
 Note that this *includes* changes to a wiki. It's not cheating because GitHub wikis are themselves git repos. Including wiki work gives you a way to have days where the work you did was primarily thinking, not typing, but it still makes you write down at least some of what you thought about.
diff --git a/hundred-day-hacking.md b/hundred-day-hacking.md
@@ -0,0 +1,15 @@
+# One Hundred Days of Hacking
+
+## Objective
+
+Get better at some aspects of creating software by doing them more regularly.
+
+## Inspiration
+
+A friend of mine, as a way to "level-up" her young daughter at violin, set a goal that the child would practice every single day for 100 days, without a break. This seems like such a good idea that I decided to steal it. 
+
+## The Rules
+
+Every day, for 100 days in a row, create a new commit somewhere on GitHub. It can be of any size, on any project. If you miss a day, start the count over. 
+
+Note that this *includes* changes to a wiki. It's not cheating because GitHub wikis are themselves git repos. Including wiki work gives you a way to have days where the work you did was primarily thinking, not typing, but it still makes you write down at least some of what you thought about.