Working on the final project in the web security section of the Node.js course from The Odin Project. I added a test user account with the app’s sign-up form. I was able to successfully login but then started wondering how I would handled failed attempts and authorization issues. I had not added a task for building out the error handling for the application. I also forgot to include the handling of 404 errors.
The key takeaway from this – all authentication / authorization features come with their matching error handling concerns. Not error handling from the code but rather from the User. I have not put much thought into this with backend application yet. There is a lot to consider but I am sure that there are core staples that need to be addressed with all applications. I wonder how these are planned out or tested at scale. Right now I am only dealing with 404 - Page not found errors and 401 - Unauthorized errors. I wonder what else I am missing. I guess I will just have to build more projects to find out.
TLDR;
Okay, so here are the highlights of what I did:
- Backend -> Continued working on the Members Only Project from the web security section. Added the login and sign-up views and finished tested them. Worked on the error handling but I realized I need to do some quick notes on the
ejsandhttp-errorspackages.
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.