Once in a while, you do or are forced to return to the basics. Doing so refreshes your perspective, reminding you how it all started and where you are now.
TLDR: To continue exploring CloudFlare cloud platform, to my convenience my next project is a service which shortens url's to my need. The end project is here: https://shurl.pages.dev. To remember it effortlessly lets call it shurl which stands for short url. Minimal UI is provided by concrete style again. What we need for this project is a landing page where you are instantly offered to create a short url, a backend function to save it, and a backend function to visit the shortened url.
This is a follow-up article to A full-stack developer's shift to serverless paradigm, which explores the spontaneous allocation of project resources. To fully grasp the context, familiarity with JavaScript, its ecosystem, npm, and web development concepts is recommended. However, feel free to proceed at your own pace.
It's been a while since I truly grasped the concept of serverless computing. However, transitioning from managing servers to embracing serverless practices demands more than just understanding its definition. It's about challenging yourself to approach tasks in entirely new and unconventional ways.
Transitioning between development teams and embracing new disciplines often exposes us to a myriad of diversities that can significantly influence where we choose to invest our focus. It's not uncommon for engineers to find themselves developing intense obsessions, and one of the common areas of fascination is tooling. While there's a multitude of domains to explore, this article is dedicated to improving your ability to navigate the fog that arises when you encounter a mesh of tools, which, ideally, should seamlessly blend into your daily development routine.
The recent events in the tech industry, where companies have faced consequences for failing to act but have gained wisdom afterwards, have inspired me to reflect on my own experiences. In particular, I want to address my failure to publicly give a farewell to a company that Arbnor Gashi and I co-founded.
In the past two decades, humanity has been focused on promoting rapid technological advancement, and we have embraced the idea that it's okay to "move fast and break things." This has allowed many apps and hardware products to fail and reach the surface, and we have been totally okay with it.
Struggling around to get through your first day with Docker? It really kinda is frustrating. Add a few more tools that you just met and that's how you start burning out. To cool it down a bit, I will list a few hints I wish someone gave me when embarking a Full-Stack role including some minor DevOps tasks that keeps you going.