Paused on the final project in the web security section of the Node.js course from The Odin Project. I Took some time to write notes on the http-errors package since I am using it for this project. I started by reviewing the notes that I had already written on the topic. Once I reviewed the notes I decided that this might be a good package to try and breakdown just like how I did with the passport package. I got out my reverse engineering hat and started looking through the package’s code.

The package is very small and does not have a ton of dependencies. Additionally, it only exports a few things. I need to go through the core functions being called but at the surface level this seems much more manageable than the passport package.

The reason I decided to dive deeper was to see if the first package breakdown was a fluke. I think that being able to read other people’s code with minimal context and being able to understand what is happening is a key skill I need to improve on. I am used to tutorials and articles that help to explain topics but I have recently encountered more and more packages or libraries that are outside of the popular content sphere and have less than adequate documentation. So in working with those tools I need to be comfortable just reading the code.

Hopefully this goes well and does not take long.

TLDR;

Okay, so here are the highlights of what I did:

• Backend -> Paused working on the Members Only Project from the web security section. I am taking some time to read through the code in the http-errors package.

---

---

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.