100 Days of Code is a challenge/community, where you publicly commit to code for 1 hour for the next 100 days (it is however more flexible than that). You also become a part of a large friendly dev community.
Two Main Rules:
- Code minimum an hour every day for the next 100 days.
- Tweet your progress every day with the #100DaysOfCode hashtag.
Replies
Best
For people with a lot of time constraints, 1 hour a day is hard to set aside. Perhaps 100 concepts in 100 days? Also, no offense as it is a decent pattern, but this seems more of a template that can of course be applied to other endeavors. :)
Report
100 Days of Code is a great accountability tool. I found the community on Slack and Twitter to be very supportive.
There are no drawbacks as such, but I did notice that people sometimes spent more time than I thought they needed to agonizing over what really counted as a day of coding, whether they needed to start over from the start if they missed a day or two days, whether they could take short break for a family vacation and still continue a streak, etc. It's a public accountability tool, but in the end, you're only really accountable to yourself. Do what feels right, but honest and upfront about it. That's it.
Pros:
A great, supportive community (at least when I was using it)
Replies
100 Days of Code is a great accountability tool. I found the community on Slack and Twitter to be very supportive.
There are no drawbacks as such, but I did notice that people sometimes spent more time than I thought they needed to agonizing over what really counted as a day of coding, whether they needed to start over from the start if they missed a day or two days, whether they could take short break for a family vacation and still continue a streak, etc. It's a public accountability tool, but in the end, you're only really accountable to yourself. Do what feels right, but honest and upfront about it. That's it.
Pros:A great, supportive community (at least when I was using it)
Cons:None.