Reading the Two Rules of #100DaysOfCode Like a Product Spec
A teardown of #100DaysOfCode: who checks, what counts as a day, what a miss costs, and how a hashtag challenge differs from one with video proof and a stake.
In this article7 sections
#100DaysOfCode was written down as two rules and one small exception. It runs on a hashtag, with no app and no enforcement. That makes it easy to see where its accountability actually comes from.
Nearly everything below comes from Quincy Larson’s freeCodeCamp history of the challenge, written when thousands of people were tweeting the hashtag hundreds of times a day. Alex Kallaway had emailed Larson about the idea in June 2016. As Larson tells it, Kallaway struggled to code consistently after work and kept choosing TV instead. The 100 itself was a spouse’s suggestion.
What are the rules?
- Code for at least one hour every day for 100 days.
- Each day, encourage at least two other participants on Twitter.
Skipping a day here and there for unplanned situations is allowed. Not more than that. Finishers can start a second round, and the daily tweet carries a counter in the form R#D#, so Round 1, Day 1 is R1D1. By tradition, Round 2, Day 2 gets a picture of R2D2.
What does it check?
Nobody. A tweet saying “R1D14” is a claim. Larson’s history points participants to a GitHub repository as a progress journal, which adds a timestamp trail, but a commit is not proof of an hour. What carries the weight is plausibility: a hundred consecutive daily posts make a record that is awkward to fake and possible to.
That is a choice rather than a flaw. A rule that required verification would have needed a verifier, and a verifier is a person or a program that someone has to run.
What is a day?
One hour of coding. Time in, with no output required. Kallaway’s motto, as Larson records it, is “Every day you code is the day you’ve won.” The unit is generous on purpose: an hour of confused reading counts the same as an hour of shipping. That generosity is why people finish, and also why a finished hundred days can leave you with no working project. The rules make no claim otherwise.
What does a miss cost?
Less than you would expect. The tolerance clause lets you skip occasionally, and nothing else is on the line: no fee, no reset. Your penalty is a gap in a public counter that you will see and your followers might.
Larson quotes Kallaway saying that “New Years Resolutions don’t work because people over-commit.” The tolerance clause is the remedy for over-commitment, and it gives up the consequence that would make a miss sting. The challenge trades bite for survivability. For someone learning to code after work, that trade is probably right.
Why is rule two the interesting one?
Rule one is the habit. Rule two is the audience.
Requiring everyone to encourage two others daily means the community supplies its own witnesses. If a thousand people follow the rule, two thousand encouragements are owed every day. Nobody has to recruit an accountability partner; the rule obliges you to encourage two others, and the same rule obliges two others to encourage you. Kallaway told Larson that “Accountability is one of the biggest factors in trying to change some aspect of your life,” and rule two is where that belief became procedure.
The weak spot is attention. Encouragement is cheap to send and easy to ignore, so the rule guarantees that a reply exists, and it cannot guarantee that anyone misses you if you stop.
How does it compare with a challenge that has video proof and a stake?
| #100DaysOfCode | A video-proof challenge with a stake | |
|---|---|---|
| Who checks | Peers, on trust | Friends you picked, who watch the proof |
| What counts | An hour of coding, self-reported | Whatever you and your friends agreed to film |
| Cost of a miss | A gap in a public counter | A penalty known before you start, such as a random photo shown to your group |
| Cost to join | Free | Free to watch; paid to run your own |
| Reach | Anyone using the hashtag | Only the group you invited |
DontSnooze is the right-hand column. The hashtag wins on cost and on strangers; DontSnooze is iOS-only, and starting your own challenge needs Pro ($8.99 a week, $17.99 a month or $59.99 a year).
What the right-hand column adds is a person who can see that you did it, and a miss with a known cost. Someone who has only ever tried free hashtag challenges should start there. The evidence on cash versus social stakes is worth reading once the free version has stopped working for you.
What does the spec leave out?
Larson’s history cites no controlled study of #100DaysOfCode. It offers testimony: participants say it carried them through months-long barriers, and some credit it with a first developer job. Testimony of that kind comes from people who finished. The ones who stopped at R1D9 did not write follow-up posts.
If you borrow the idea for a non-coding habit, copy rule two before rule one. Swapping the hour for a run or a page is easy. The two daily encouragements are the part that keeps it from being a solo project with a hashtag on it.