Why I’m doing #100DaysOfCode

Sharing is Caring

I have been professionally programming for about 10 years or so. I created my first website at least 12 years ago back when html consisted of font tags everywhere and flashing marquees that thankfully fell out of style. I wrote my first JavaScript around 2000 or so, but I never really felt that I really understood JavaScript. This past year in a lot of ways has been pretty painful as JavaScript to me ended up mostly meaning mostly jQuery. In April 2016, I started a new job where we have been mostly writing JavaScript, and going completely serverless.

I’m devoting my #100DaysOfCode of code to writing as much vanilla JavaScript as possible and then moving onto a lot of React. As per the rules, I won’t be counting any of my time spent at work or any time doing tutorials. I don’t feel that I need to spend a lot of time doing tutorials anyway, I need to spend time writing code and perfecting my craft.

How to get started with #100DaysOfCode

Alexander Kallaway has written quite a bit about How to get started with #100DaysOfCode, but the basics are as follows:

  • fork this repo: https://github.com/Kallaway/100-days-of-code
  • Read the readme from the forked repo and follow those steps.
  • Mention to the world that you are doing 100 days of code, via twitter or facebook.
  • Constantly update your git repo

Follow me on twitter to see how I’m doing, and what I’m working on.

Author: Brian Cline

Brian is a programmer living in Niagara Falls with ten years of development experience. He is passionate about automation, business process re-engineering, and gamification. For the last six years or so, he has been working with Salesforce and JavaScript.

Related Posts

Sharing is Caring

Comments are closed.