The concept behind the 100 Days of Code Challenge is simple. There are few rules. After participants have made a public commitment to do so, they must do so every day for 100 days
- code for at least one hour,
- write a tweet with the hashtag # 100DaysOfCode that documents your progress,
- Exchange ideas with at least two people who are also taking part in the challenge.
It doesn’t matter whether you’re an absolute newbie or an experienced outstaffing developer who just wants to learn something new – everyone can take part. The choice of content is entirely up to the participants. Studying a Python tutorial is just as legitimate as dealing with complex data structures, learning Git or loosening up the process with an educational game in between.
Some programming practice can’t hurt!
Public obligation – even if it’s only Twitter
The public commitment via Twitter should help with perseverance. Basically, nobody prevents me from simply quitting – but the daily tweet and the exchange with others should prevent that. Optionally, the challenge suggests keeping a kind of diary about what worked, what didn’t and where there is a problem. There will therefore be a weekly update on t3n.de about how the challenge is going for me. There will soon be a profile on GitHub with projects that arise during the challenge. You can follow my Struggle on Twitter. Of course, I’m happy about fellow campaigners – you can read everything there is to know about the challenge at this point.
Suitable for this: