Rules of the 100 Days Of Code Challenge
I will code for at least an hour every day for the next 100 days.
I will be focused on the projects defined in #100DaysOfWeb in Python by TalkPython and PyBites.
October 16th, 2019.
- I will tweet about my progress every day -> using the hashtag #100DaysOfCode
- If I code at work, that time won't count towards the challenge.
- I will push code to GitHub every day so that anyone can see my progress and add a link to the commit.
- I will update the Log with the day's progress and provide a link so that others can see my progress.
- I will work on real projects, facing real challenges. The time spent doing tutorials, online courses and other similar resources will NOT count towards this challenge. (If you've just started learning to code, read FAQ). I will be focused on the projects defined in #100DaysOfWeb in Python by TalkPython and PyBites, though. I will not count the time watching the videos, but the time working on the projects. The videos are introducing technologies that are supposed to be applied in the project that follows.
Ideas to make this challenge more effective
- To increase the chances of success, it's a requirement that you add a link to each of the day posts in the log. It can be a link to a commit on GitHub, a link to a blog post
- If you get upset or stuck, read this article: Learning to Code: When It Gets Dark
- If you don't know why there is such an emphasis on working on the projects vs doing tutorials or online courses, read this: How to Get a Developer Job in Less Than a Year
- If you can't push your code to GitHub for some reason (e.g. if you're only starting to code and doing interactive exercises), provide a link to a tweet. You can think of something else as long as your challenge stays public - and you get the benefit of being committed to it and accountable for your progress.
- Another good bonus of forking this repo -> if you haven't worked with Markdown before, it's a good way to practice.