#100DaysOfCode

The Official Website for the Challenge


Welcome! Here you can learn the rules, get answers to your questions by reading the FAQ, and find out more about the community that's growing around the challenge.


Two Main Rules

  1. Code minimum an hour every day for the next 100 days.
  2. Tweet your progress every day using the #100DaysOfCode hashtag.

Why 100 Days of Code?

Here is a video where I explain how the challenge came to be, the reasons behind it.

If you have any questions or ideas about 100DaysOfCode (or other ideas), feel free to reach out to me on Twitter: @ka11away

Publicly commit to the challenge:

If you made the decision to commit to the challenge, Click here to tweet it to the world, making yourself accountable and taking your resolve to the next level! Tweet


Here is the live timeline of the activity of the #100DaysOfCode community on Twitter

#100DaysOfCode Tweets

Next Steps

If you've decided to join, here are the steps you need to go through:

  1. Read Join the #100DaysOfCode and Boot Up 2017 with the #100DaysOfCode Challenge
  2. Fork this Github repo and commit to the Log daily. Example.
  3. Code minimum an hour every day for the next 100 days.
  4. Delete the examples in the log, or comment them out, and start filling it with your own content.
  5. Tweet your progress every day using the #100DaysOfCode hashtag.
  6. Follow 100DaysOfCode Twitter Bot that retweets all the tweets that contain the #100DaysOfCode hashtag. It's a great way to keep yourself motivated and to participate in the community. Thanks @amanhimself for creating it!
  7. Important: Encourage others who are doing the same challenge on Twitter or elsewhere - by giving them props when they are posting updates on their progress, supporting them when things get difficult. Thus we will grow a community that is helpful and effective, which will lead to a higher success rate for each person involved. It's also more likely that you will stick to your own commitment, given that you will get acquainted with a couple people (or more) right away.
  8. If you find a great, helpful resource that others would benefit from, either submit a Pull Request to add it to the repo, or just tweet at me (see info below)