My #100daysOfCode Challenge

Published: Wed 08 August 2018

100 days of code

The 100 days of code challenge is becoming more popular by the day. It was started by Alexander Kallaway as a way of forming a habit, one of regular coding. More developers seem to be committing to the challenge daily.

Starting the challenge has been on my mind for a while now, and I've finally decided now is the time to commit to it. Today is my Day #1. You might be wondering why I decided to join #100daysOfCode? Or what do I plan on doing during the challenge? Well, all is answered below. This, of course, will likely change as the 100 days progresses. So to keep up, check back to this blog regularly or follow my #100daysOfCode Github repo.

(If you have never heard of the challenge, you can find the official rules and FAQ here.)

Why take the challenge?

Because I need some structure! My life is hectic, at best. So I need social accountability (otherwise known as positive peer-pressure) to get shit done, sometimes. It's how I wrote my first book!

This will also help me take steps to build my portfolio, friends, and confidence as I aim for the next level in my career as a developer.

The (modified) rules

I've taken the liberty (like many before me) to modify and extended 'the rules'. The rules below extend the official rules of the challenge.

  1. I vow to code for a total of one hour per day. This will be done in one or more sessions.

  2. This coding time will be used to build portfolio and personal projects, and not client work. It may include tutorials that involve following along while coding. Just watching the videos doesn't count. Writing pseudocode does count.

  3. Writing coding tutorials for my blog may count towards the total time, but can not make up more than half of the total time spent (30 minutes max).

  4. On travel days I will miss no more than two full days consecutively. Any days missed will be added onto the end of the challenge until 100 coding days has been reached.

  5. Acceptable reasons for missing a day:

    • Traveling on plane/train/car over distance.
    • Nursing sick children.
    • Loss of limbs / or serious hand injury.
    • Death.
  6. Code is to be pushed to Github or Bitbucket (for private repos) daily. Not all code will be in my #100daysOfCode repo. Projects may require their own repo, in which case the links to those will be placed in the on this file.

What will I build?

I have a few ideas. Some are mentioned on the repo for the challenge. Some, well, will be private. Not everything has to be open-source and free. ;)

One thing is for sure though, I will be starting the challenge with the Real Python Course. Some of it, admittedly, might be aimed at someone a little newer to programming than I. But practice is practice, and I'm sure I'll get plenty out of it all the same. I intend to share some of the things I've learned on the course on this blog.

In the spirit of transparency, I do work for Real Python as their Community Manager. The copy of the course I have is an advance copy of the newest version of the course, which I'm told has had major rewrites and will be released at some point later this year. I plan to be honest in my assessments and reviews, however, as I know my feedback will help improve the course for future Pythonistas.

Ready, Set, Go...

I guess the only thing left is to start coding! You can check my daily progress on Twitter (as per official rules). You can follow me on twitter, or search the hashtag #100daysofcode for updates.

Are you doing the challenge? If so let me know in the comments. Any advice you have will be appreciated :).

Happy coding.