100 Days of Code

This challenge is about spending at least an hour each day learning and/or working on coding. You can do this challenge at any skill level because the point is for you to commit to making yourself a better developer. The most difficult part will be sticking with it, it is okay to miss a day here or there, but try to make up for it at the end.

Another big aspect is sharing your progress publicly. This allows you to showcase your hard work, and it will help keep you motivated. You can use the hashtag #100DaysofCode on Twitter to write a quick summary of your progress each day. I prefer using GitHub as a record of my progress, as it allows me to link to what I’ve been working on.

This challenge might seem intimidating at first, but even a thousand mile journey begins with a single step. It is definitely something that might be hard for you to start each day, but if you stick with it, it will become easier and easier and you will be able to improve as a developer faster than you think. Feel free to share what day your on or links to your Twitter, GitHub, or anywhere else you like!

100 Days of Code on GitHub

To set yourself up for this challenge using GitHub as I have, you first need to create a new repository with a README, mine is called ‘code 100’. Then you’re going to edit the README to include some markdown language for Links and Headers. For example:

# 100 Days of Code {This would be your main title}
## Projects {This is a subtitle with a line separating sections}
### [Your Project Title](https://yourwebsite) {This is a link to a project}
 {This is an image}

And finally, you would update this README file each day with a brief summary of what you’ve done for the day. You can keep adding links to new projects, or screenshots, or videos or anything else you want.

Here is a link to the complete GitHub Markdown Cheatsheet