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.