A New Mother#^@%*&ing Website

I had just recently started my internship and started to get to know my fellow interns a bit more. We started to share various social medias that we could be found on. This was nothing but a veiled attempt to “network” with people we could one day ask for a referral in case they make it into a FAANG. While this was all happening, we also started to take a look at everyone’s websites. Having a domain and a website is dirtcheap these days and everyone should have one. Nothing cooler than owning your very own piece of land on the internet. However, small it may be.

Getting back to our websites, there was one thing that I and many other interns found in common about our wesbites; they were nothing more than glorified portfolios for recruiters to gawk at and we all went to great lengths to make them gawk. CSS Transitions, expansive panoramas of landscapes, and Fontawesome icons lathered across the DOM but performance and bundle-size be damned. It was quite a sight (ha!) to see as website after website I saw variations of the same type of template. And let’s be clear, mine was no better. If anything, it was the worst offender. There were, peppered within a sea of these bloated portfolios some that were so incredibly minimal and lightweight (and they didn’t implode when you disabled js!). Now mind you, these aren’t front-end developers where their entire profession is based on making the visitor “ooh” and “ahh” at their mastery of frameworks. But even if they weren’t front-end developers what was the point of using javascript to render their entire blog on the client-side when all it did was display some text and images.

As a response to this gross display of everything that is wrong with modern web development someone replied with just this:


I think he’d aptly made his point. I remember immediately going to my own website and cringing at this monstrosity I had created. You couldn’t even load the site if javascript wasn’t enabled. The next day I immediately started to look into alternatives. I still wanted to use some sort of a templating engine because I like the portability and modularity it gave me while still serving just html/css. I remember in one of our weekly calls Uncle Raju mentioned the Jamstack which sounded really interesting. I immediately started to look into it more and currently I am in the process of rewriting my entire website using Gatsby.js.

Hopefully I’ll have something to show for it next week, but this was definitely a wake up call for me and I hope to learn from it to make something that is a lot leaner with respect for my user’s resource. Something that I didn’t think about earlier.