I have been doomscrolling on-and-off again ever since I had Facebook, Instagram or the sorts. The last streak of mindlessly watching short-form videos every night lasted 14 months. I knew I had to quit. Watching all this dopamine laden videos had done a number on my attention span, and now I sometimes find myself switching between the tasks I was supposed to do every 5 minutes, without actually getting anything done, and inevitably resulting in me swiping on Facebook Shorts for 3 hours straight. ¹

In the previous part of this series, we looked at how one may go about to improve the build time of your Node.js Docker container. In this part, I will go more in depth with regard to the size of your container.

As one of the most popular backend tech stack at the moment, containerizing Node.js is still a chore for most developers. Here is my attempt to present a guide on how to do it, efficiently enough for production.

We have all been there. You earn that lucrative IT-sector big buck, and next thing you know, you are down to 10% of your earning by the middle of the month. You don’t even know how you spent the money. Then you can only vaguely recall buying some shirts and shoes and some newest technology thingamajigs. “What the f#*k did I spent this half a thousand buck on?” is the question that stuck will in your mind until next month, and then the cycle will repeat.

I was writing some scripts to attach i18next to Bubble. Long story short, we have to ensure the library is loaded, i18next is initialized before rendering the page. I handle this by creating a custom component to check whether i18next is ready, optionally load some more namespaces, finally expose an is_ready state. The remainder of the page should only be visible when the Loader component says everything is kosher.