100 Days of Code. Is it worth it?

What is the #100daysofcode challenge?

On January 3rd, 2017 I joined a multitude of coding newbies and seasoned programmers for the 100 Days of Code challenge. The rules were pretty straight-forward. We would work on coding projects for one hour every day for 100 days. In addition to the projects we would log our progress on GitHub and post about it on twitter to keep each other accountable. Study time and work projects did not count toward our hour. The complete set of rules and guidelines can be found here.

Is it worth it?

For me #100daysofcode has been a great motivation to actually create projects with code. I began my coding journey in August 2016 with
freeCodeCamp. I powered through the HTML and CSS sections and completed the first two projects quickly. But I soon became lost and stuck on the basic JavaScript section. This definitely put a damper on my motivation. I kept going back and doing tutorials for HTML and CSS on various websites because it was familiar and easy for me. I realized my coding was becoming static.

Around December 2016 I saw a job listing I was interested in. To my dismay my portfolio was seriously lacking projects. So I rushed to build a few web apps to show the prospective job what I knew. This was not the best idea but it did push me to get out of my comfort zone and gave me the desire to build projects. Shortly after this experience, I read about the #100daysofcode challenge. It really got me excited to level up agian. I liked how Alexander Kallaway (the guy behind #100daysofcode) suggested taking a few days to think about the challenge and not just rush into it. I know I have a tendency to jump in and start a project when my interst is piqued but my motivation usually fizzles out quickly (as my many half-finished crocheted projects can attest). So I took his advice and prepared myself for the next 100 days. I worked on understanding line command, git, and GitHub because I thought they would be important to use during the challenge (they have been). I also talked a lot about it with family and friends so that I really didn’t have a choice to back out.

I am now 60+ days into the challenge and I would say it has completely been worth it. Through this challenge’s twitter group I found the #dailycssimages challenges that really sparked my desire to code fun and exciting projects. I have a better understanding of advanced CSS like animations and transition. I have learned how to deploy sites with Jeykll to GitHub pages. I contributed to my first open source project and I am currently learning Vue.js. Best of all, I now have a lot of projects to add to my portfolio.

Should you join?

If you are feeling stuck with your programming progress or if you just want motivation to work on side projects #100daysofcode is a great challenge to join. The community is very encouraging, even for code newbies. So if you want to level up, join. You won’t regret it.


2 Comments 100 Days of Code. Is it worth it?

  1. a. chigozie March 20, 2017 at 10:21 pm

    I can totally relate to wanting to apply to a positions but not feeling confident in your portfolio. I’m going to start a different challenge, 100 Days of coding is pretty aggressive for me now since I’m job hunting but having support is definitely helpful I’ve noticed. I totally lapsed on my first 100 days of code challenge, but will look to try again later.

    1. Christina March 20, 2017 at 11:44 pm

      It’s definitely hard to keep up with if you have other big time obligations. I know a lot of people are doing this challenge http://benjaminspak.com/challenges/301-days-code/ . It doesn’t have a set amount of time you are supposed to code eaach day but still seems to have a good support group. It might be a good option for you. Best of luck on your job search.

Comments are closed.