Today is January 3rd 2017, and this is Day 1 of #100DaysOfCode challenge. It all started a week ago when I read a blog post on FreeCodeCamp’s blog, written by Alexander Kallaway titled as Boot Up 2017 with the #100DaysOfCode Challenge. It inspired me to start off 2017 with the #100DaysOfCode Challenge.
Before diving deeper into this article, a little bit about me. I’m a programmer (have been into Web Development, but currently looking to shift to mobile app development). So, I am going through a transition right now.
The main reason for doing this #100DaysOfCode challenge is that I’m rarely willing to share my work via public repositories on Github or write about the process consistently. I think that this challenge would make me more accountable, and improve my comfortability with using Git as version control. Also, the #100DaysOfCode challenge is a part of my New Year’s resolution which includes a bunch of other things as well. I’m calling 2017 — "A Year Of Code".
Another reason for taking the #100DaysOfCode is to improve my iOS App Development skill. A couple of months ago, I decided to learn iOS App Development with Swift. But back then, I had to appear in my GRE and TOEFL tests, so I didn’t had enough time to learn iOS App Development. I have to admit that I’ve been struggling to keep learning iOS App Development since I’ve been really busy in other things. And I still consider myself as a newbie in iOS App Development.
To be honest, in the 2016, I have not actually coded anything worthy enough to be noticed, because I was so busy preparing for GRE and TOEFL that I didn’t had any spare time to work on my programming skills. So, this is the time when I am going all out and actually coming out of the #100DaysOfCode challenge as a better programmer.
About My Progress:
Today, on Day 1, I went through some Swift 3 tutorials from Treehouse’s Swift Track. Also, I worked on my portfolio site, I worked on CSS. It will take sometime to build the complete portfolio website though.
I have pushed the code to my Github repository, and updated logs to make sure that I keep track of my progress. I know that in order to complete the #100DaysOfCode challenge, I need to follow certain guidelines and strictly commit to writing code every single day.
Be sure to check out my #100DaysOfCode Github repository. If you like this repo and find it useful, please consider ★ starring it (on top right of the page). 😊
If you’re also taking the #100DaysOfCode challenge, let me know. We can hangout sometime, and talk about each other’s progress on Twitter. Follow me on Twitter and Github.
It's been about 10 days since I started the #100DaysOfCode Challenge. Here is my progress up until now:
- #100DaysOfCode Day 2: Messing with CSS
- Day 3 of #100DaysOfCode — Find The Bug
- Day 4 of #100DaysOfCode — Style it like a Boss
- Day 5 of #100DaysOfCode — Eat.Sleep.Code.Repeat
- Day 6 of #100DaysOfCode
- #100DaysOfCode Day 7 & Week 1 Progress Summary
- #100DaysOfCode Day 8 & 9 — Dealing with Frustration