I switched back to my Backend Development study track for the weekend. I got back to the API development section from The Odin Project’s Node.js course.
I started reading the documentation for the CORS package that is used in tandem with the express framework and Node.js. It was not too difficult to understand the actual code however, the underlying concepts still kept me doubtful. Learning about CORS feels similar to when I was learning about HTTP requests and servers. Everything seems so foreign but once you take the time to get used to the syntax, protocols, common header names, and examples things start to make sense.
The concern that I always have with jumping into using convenience libraries like express and CORS is that a lot of the nitty gritty underlying code is abstracted out so understanding what is really needed to make things work becomes harder to understand. Maybe it is just me but I am not a fan of black boxes. So, although I spent time reading the package’s documentation today, I am more interested in spending time noting down the concepts and processes at work. I want to be flexible with what packages I use and the only way I can do that is by understanding the underlying concepts and not pigeon hole myself with one particular tool.
TLDR;
Okay, so here are the highlights of what I did:
- Backend -> Continued going through the material on API development with
Node.jsfrom The Odin Project’s backend development course. Read through theCORSdocumentation on the Express.js website
Goal For Round 8 of the #100DaysofCode Challenge
This is my eighth round of the “#100daysofcode” challenge. I will be continuing my work from round five, six, and seven into round eight. I was working through the book “Cracking the Coding Interview” by Gayle Laakmann McDowell. My goal was to become more familiar with algorithms and data structures. This goal was derived from my goal to better understand operating systems and key programs that I use in the terminal regularly e.g. Git. This goal was in turn derived from my desire to better understand the fundamental tools used for coding outside of popular GUIs. This in turn was derived from my desire to be a better back-end developer.
I am currently putting a pause on the algorithm work to build some backend/full stack projects. I primarily want to improve my skills with the back-end from an implementation perspective. I have improved tremendously in terminal and CLI skills but I lost focus due to how abstract the algorithm concepts got. I wanted to work on things that were more tangible until I can get to a position where I could directly benefit from improving my algorithm skills and theoretical knowledge. So that’s the focus right now. Build my backend skills and prove my full stack capabilities by building some dope projects.
Again, I still have no idea if my path is correct but I am walking down this road anyways. Worst case scenario I learn a whole bunch of stuff that will help me out on my own personal projects. Best case scenario I actually become one of those unicorn developers that go on to start a billion dollar company… You never know LOL.