Photo by Paul Morris @ Unsplash

After 200 Days of Code…


If you want the takeaways, here are 4 points without having to read the whole article. Number 1, React will help improve your JavaScript (Tip: learn basic ES6 before you start React). Number 2, build projects with new technologies and set actionable deadlines for them. Number 3, focus more on the code aspect instead of styling because there might be designers for that. Number 4, give Manjaro Linux a try if you’re sick of Windows (if you have a Mac, it’s already pretty good as is).

If you’re still here, you probably want to read the article. Here we go…after building a ton of momentum from the first 100 days of code, I wanted to go for round two. A lot of people want to use R2D2 in their tweet but I just prefer the plain 101 to 200. The second round was quite productive as I built up our Free Code Camp local group, switched to Manjaro Linux from windows for a better dev environment, finished a couple of online courses, and built 3 new projects. This was my first foray into ES6 and React and it has certainly been an awesome ride. What I thought was going to be a brick wall turned out to be a new love for writing React component pieces and connecting them together like a puzzle. It was also a lot easier to deal with when you can just work on one aspect of your app at a time instead of looking at one big file of JavaScript. Here are some significant things that happened on my second round of #100DaysOfCode:

Days 101 through 125

I started working on the Free Code Camp Wikipedia app at the beginning of this challenge and finished on day 118. To assist with the challenge, I took a free course called Asynchronous JavaScript Requests from Udacity which helped out a lot! I wanted to get a better handle on AJAX (or more properly, AJAJ), Fetch API, and dealing with promises. On day 109, I also started Wes Bos’s ES6 for Everyone to prime myself for React. This is one of the best courses I have ever owned and still reviewing it after my 200 days of code (there’s a lot that came with ES2015/ES6). I do firmly believe that having a good handle on var/let/const variables, scope, spread operator, destructuring, classes, looping with .map/for in/for of, understanding Object.keys/values/entries, and other basic ES6 concepts will help you immensely with React. After all, React is JavaScript at the end of the day and consequently will make your JavaScript better too.

I did started a free React course on Edx but ended up trashing it since I did not enjoy the pace. There was a lot of copy-pasta code to build a Connect 4 game and I simply didn’t learn that way. During this time, I also switched over to Ubuntu Mate since my Windows 10 had an annoying message to upgrade. It was not too difficult to get use to Linux since the development environment was closer to Mac and I liked it much more than windows actually. Our Free Code Camp Ashburngroup was just slowly starting up too and I started posting more about our meets, setting up the facebook group, and building our local website.

Days 126 through 150

This quarter of the leg, I started on the Free Code Camp Twitch API app. I knew it was going to be more of Fetch API so it was going to be a quick project and I finished on day 130. I started doing HackerRank challenges but evertually stopped since the UI was overcomplicated (CodeWars is a better platform anyways). My friends and I also attempted to work on a project and do interview prep together but it eventually failed as other things took priority. On day 141, I switched over to Manjaro Linux which was so much better than Ubuntu Mate. Some of the features I loved were Yakuake (a persistent terminal), multiple window switches (try the Desktop Cube Animation, pretty slick), Octopi software manager (watches all your software and informs you of updates), and just the beautiful UI that came with the KDE install.

Also, I had a job interview for a front-end web developer position on day 145 to build websites with their stack: JavaScript, PHP, and Bootstrap. The company had a couple more rounds of interviews and would let me know in 2 weeks. Unfortunately, I never heard back from them. I proceeded to start Learn React.js, an introductory course on Lynda made in 2016, but it was using old syntax like React.createClass (where most people use stateless functional components or ES6 classes now). I still pushed through it but it was tough trying to discern between old syntax versus new. If you ever do find yourself working with old React code, react-codemod is a godsend and helps convert your syntax. It helped me launch the notepad app from that Lynda course actually.

Afterwards, I started React.js Essential Training Course on Lynda on day 148. This course was much better but still didn’t get into a lot of depth. As a general opinion, courses never go into a lot of explanation or best practices. Some of the courses are hit or miss since they might be older. This was my experience with some of the other courses on there as well. The courses explain some topics well but gloss over the others. The format feels more like watch-me-code and learn. I don’t know about you but I learn better if it is explained well and if I code something myself. I shouldn’t complain since my library offered the subscription for free (your library might have it too, you should check). They have other cool stuff on there anyways which I hope to check out in the future.

Oh, and I completed all my Pharmacist CE credits too and all 15 long articles with a pass/fail test at the end, but not that it’s important to you. Haha

Days 151 through 175

I started a photography website for a friend to try out Materialize CSS and an Instagram API. I made a kick-butt contact form for it too. I finished the ReactJS Essential Training course on day 157.

Then came the intership company in Ohio. I had an online interview and they wanted to see what web app I have completed. Up to this point, I only had the Twitch API app that I built. So I came up with the idea to build a project in React for an event management system that I mentioned during the interview. I strapped down for 1 week and really learned React. It was amazing what I picked up under a time constraint. I built the best thing I could and sent them an email. Unfortunately, I never heard from them. That was okay because I learned a tremendous amount of React anyways and it eventually lead me to to more of the React ecosystem and Firebase too.

We continued our regular Free Code Camp meetups during this period. At one event, we even had record-setting 7 devs turn up. It was also my birthday and Christmas season so there were a lot of different festivities. I got deeper into Firebase and learned a lot about data structure manipulation too.

Days 176 through 195

At this point, I was stuck on my React app, Respondez. I didn’t quite know how to do deep state manipulation in React (which you should not do by the way). Yet I was stubborn and didn’t know any better. Eventually, I changed gears to take a break. I went after a lot of algorithms on Free Code Camp and Codewars to try to deepen my JavaScript understanding. In the meantime, I started Wes Bos’s paid React For Beginners course so I can keep my React skills sharpened. I pretty much finished the course on day 180 but some of the code I couldn’t figure out how to tie in with Firebase even after re-watching/research.

I continued with the momentum and pushed through Wes Bos’s free Learn Redux course to see if there’s anything that would help my Respondez app. I finished the Redux course on day 191 with data from my own instagram account. Turns out that Redux is more for much larger applications and all I really needed was React’s inherent state and the update-immutable library.

I came back to my Respondez App and pushed through all the hurdles with bitten nails and pulled hairs. I’m glad I returned since you can see it for what it is today.


So that’s where I am now, just working on the app and trying to deploy it, fixing bugs, user testing, and writing an article about it. I hope to be able to launch it so other Free Code Camp groups can use it too.

The biggest thing I learned from this cycle of 100 days was to persist even harder and sometimes the most simplest solution is to push through instead of trying to look for libraries/other resources. It helps to also put self-imposed deadlines as it will help you to ship your app faster.

The next 100 rounds, I’m attempting a couple new habits. I’m working on waking up before the sun, meditating, using apple cider vinegar, adding steamed vegetable to my diet, and podcast-walking. This isn’t related to coding but I thought you should know that I have been feeling a significant gain in my productivity. I feel completely relaxed and full of energy to code and no longer take any naps. So that’s why you see the icy sunrise picture as my banner. I love waking up before the sun and the cold invigorates you (as Wim Hof would say, “the cold is your friend”).

Let’s see where I’ll go in the next round. Even though it seems that the learning never stops and that first developer job is beyond grasp, I remain hopeful and resolute in the direction I am heading. I will continue building and learning every single day. I even took a part time job to support myself so I can continue learning to code. I’m hoping to get a dev job in 3–6 months. I’m getting little offers for projects here and there but nothing to print on the headlines yet. I am telling you (as much as myself) to keep persisting. Despite all odds, you are far stronger than you know and you just haven’t realized it yet. If you need to take a day off, go for a run, watch a motivational video, or just spend some good quality time with friends away from the screen, just do it! This is a marathon, not a sprint. I’m right beside you as we keep grinding. Thank you and good luck to to all my fellow JavaScript Jedis and feel absolutely free to connect with me!

Find me on: