Yesterday I battled with node version managers. I thought I won the battle and I could continue my regularly scheduled work. I cleaned up my browsers and took notes on the challenges and resources that I used before I moved on. Went to run my project and… Node.js is not running. It just seems to stall. The ironic thing is that getting the version number works fine. When I go to the area where Node.js should be installed and try to run the executable it stalls. So nvm-windows is clearly doing something which I am not mad at. It is just not clear to me. Honestly I am just going to remove nvm-windows and go back to the LTS version of node which at the time of writing this was v16.15.1. I’m just tired tbh. The only positive take away was that I understood more of what was going on with the program than I did previously. Still not enough to figure all this stuff out but more than before so I guess that is a win.
TLDR;
Okay, so here are the highlights of what I did:
- Node Version Management -> Tried to solve the problems with why
Node.jswould not run from theCLIjust like before. Tried to understand why script were not running normally. I am sure there is something I am missing that may be obviously clear to others. - Practice -> Made very little progress working on the Mini Message Board project from The Odin Project curriculum. I got hung up on not being able to run the application in development mode due to issues related to
Node.js. What a washed day… sigh. Oh well. Hopefully tomorrow is better.
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.