/100-days-of-code

Fork this template for the 100 days journal - to keep yourself accountable

I've joined the #100DaysOfCode & #301DaysOfCode Challenge.

I'm taking up the challange to go from 100 to 301 Days Of Code, because ultimately I my motto is wanting to go beyond Design to become a Developer.

Contents

If you've decided to join:

  1. Read Join the #100DaysOfCode & #301DaysOfCode if you are ambitious.
  2. Fork this repo and commit to the Log daily. Example.
  3. Code minimum an hour every day for the next 100 days.
  4. Change the date in Rules to the day you've started the challenge.
  5. Delete the examples in the log, or comment them out, and start filling it with your own content.
  6. Tweet your progress every day using the #100DaysOfCode & #301DaysOfCode hashtag.
  7. 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!
  8. 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.
  9. 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)

Note

  • If you have any questions or ideas about 100DaysOfCode (or other ideas), feel free to reach out to me on Twitter: @ka11away
  • If you like this repo and find it useful, please consider ★ starring it (on top right of the page) :)