On January 2nd of this year, I publicly committed to joining the #100DaysOfCode challenge. It tied in perfectly with my new year’s goal of becoming a better developer and working through Free Code Camp. I couldn’t wait to get started!
— Joe Cooper @ 🇵🇱 (@_creativecooper) January 3, 2017
The following day, I spent an hour writing my first piece of code of the year. I fell in love with challenge immediately, I loved the idea of having a set hour each day where I would focus on writing code and working through Free Code Camp’s curriculum. When I opened up Twitter and posted the progress tweet for my first day, I was blown away with inspiration by the amount of people who had committed to learning code.
I was sure that I was going to keep my commitment to the challenge and see it through. What ended up happening was a little different to what I had hoped for.
I set a lot of goals for 2017, and I had a couple of projects already lined up that would push my development skills. This along with travelling full-time resulted in me really underestimating the amount of free time I would have over the first few weeks of the year.
I was optimistic however, I planned on getting back to things as soon as I finished a couple of client projects. I spent the next few weeks working through client work, and making progress with other goals, and then out of nowhere, I catch a stomach infection that renders me unable to work for a little over 14 days.
This couldn’t have come at a worse time, I was a week out from launching two projects and I’m forced to take two weeks off work. This wouldn’t have been so bad if I wasn’t a freelancer and other people could have taken on my workload, but I was completely on my own and forced to leave my clients waiting.
When I got better, my entire focus was on getting both projects finished, taking care of the-do’s that had built up over the last two weeks and finding some extra work to make up financially for this time.
Fast forward to today and here we are, it’s March 20th and we’re a little over 20% through the year (thanks to @year_in_progress for reminding me of this fact today on Twitter). I’m still just as committed to completing the #100DaysOfCode challenge as I was on January 2nd, and it’s time get things moving again.
Over the last few weeks, I’ve done days here and there, but I want to publicly re-commit myself and start from day 01 again. So as of today, I’m publicly re-committing myself to the challenge.
I'm restarting the #100DaysOfCode challenge due to a bumpy start to 2017. I'm excited to be a lot more consistent this time around! 🙂
— Joe Cooper @ 🇵🇱 (@_creativecooper) March 20, 2017
Just like last time, I’m changing the rules slightly to suit my lifestyle and work alongside my other goals a little better. For example, although this challenge is meant to force yourself to write code every day, that doesn’t go to well with my goal of spending more time enjoying the places that I travel to on a monthly basis. And as I spend most of my days writing code, it’s nice to have some time away from the screen. So I’m changing the rules to allow myself to take Wednesdays and Sundays of each week, along with any days where I’m travelling.
Here’s to attempt two of the #100DaysOfCode challenge. Wish me luck!
Featured Image Credit: https://unsplash.com/search/code?photo=5Ntkpxqt54Y