The Post Graduation Struggle and My Thoughts on Node.js/Express.js

I am a bit more stressed now than I was while I was a Flatiron student. Until very recently I struggled with what direction to take to continue growing as a developer. Since I can’t begin a new career until September, I have quite a bit of time to continue learning. After graduation I found out that there are so many (maybe too many) different avenues available to continue learning and developing yourself. Come to find out this is called The Paradox of Choice, which often leads to making no choice at all.

For a bit I dabbled into statically typed languages (C#, Java) and realized that I probably would never actually use ASP.NET or Spring unless I am employed to do it professionally. Why focus on Java when I could be building web apps with the languages I do know? I can certainly learn other frameworks if I need to. Should I just focus on Rails? What about React? Err, React is entirely front-end and I need to also focus on the back-end, which come to find out is actually my preference. Not to mention React is simply overkill for many personal projects. So I decided to set Rails and React aside for now and focus on something different that aligns with my immediate goals.

I am currently preparing for future interviews and am planning on using JavaScript as my language of preference. To make developing applications a bit more convenient and to accelerate my core JS understanding, while also preparing for coding challenges, data structures and algorithms, I decided to learn Node.js/Express.js. This allows me to constantly focus on JS and get very proficient without constantly switching in between languages and frameworks.

If I had to choose I would say I really like Node quite a bit more than Ruby on Rails at this point. Node takes a bit more legwork to get up and running, but once you do it is really quite great. One thing about Rails that always annoyed me was the sense of magic and its willingness to perform menial tasks. For the most part that is gone in Node, or maybe I just haven’t figured out the lazy way of doing things yet. I also like the fact that I am doing mostly everything by hand and it is going to force me to learn it better (haven’t looked up any generators yet). I still do actually like Rails am certainly thankful that the Rails idioms and conventions taught me a clean and common sense way of doing things.

Currently I am working on a generic e-commerce app but it will include quite a few things that have interested me for some time. Some of these items are: the Stripe API for payments, sending emails, GraphQL, file uploads and downloads and websockets. I’ll be sure to post some technical details when the project is in some sort of a presentable state.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.