Why Tech is a Team Sport!

Knowing where to start is often difficult, and it can be overwhelming. But what’s even more challenging is maintaining momentum toward your goal.

Why am I saying this? Because as a software engineer, I’ve learned that the journey doesn’t end after writing your first “Hello World.” What matters most is how you continue to evolve, learn, and grow. That, I believe, is what defines you in this field.

I began writing code in 2011 and became a professional in 2015 through my first internship. It took time and persistence to find my path. I started with C, moved on to C++ and Visual Basic, and later explored web development with PHP and other tools. During that first internship, I was eager to write code, but instead, I found myself in the IT support department. Initially, it felt like a detour until I was introduced to server management. At the time, I only had a theoretical understanding of operating systems: memory management, process handling, and so on. But that hands-on experience shifted my perspective and ignited my passion for what we now call DevOps.

Since then, I’ve embraced one key principle: as a software engineer, your learning only ends when you do. No project, team, or department is ever too small to teach you something. And often, the most valuable lessons come from peers, not textbooks.

That said, how realistic is it to learn everything alone? In my view, it’s nearly impossible. It’s like trying to win an entire football season as a one-man team.

After graduation, I co-founded a tech startup with colleagues. At first, things were exciting! youthful energy, big dreams, and confidence. We succeeded in getting our name on the map, gained clients, and built real products. But when I joined a more diverse team later on, I began to recognize the gaps in my knowledge. That experience pushed me to challenge myself further, leading to my decision to pursue a master’s degree outside my home country.

Studying abroad, particularly in Italy, came with its own set of challenges, especially managing academic life in a new environment while continuing remote work back home. I realized I was falling into a comfort zone again, the very space I had worked hard to escape. So a few months ago, I leaped: I started from scratch in a new environment and focused on solving problems I identified here. Since February, my new project has been running in test mode, and so far, it’s going well.

But I’ve also learned this: you can’t stay in your league and expect to grow. This led me to reflect, do I need to relocate again for new challenges? The answer is both yes and no.

Yes, because social and survival skills are as vital as technical ones. The more you cultivate them, the more adaptable you become anywhere in the world.

No, because in today’s connected world, you don’t always need to move physically to grow. I can call anywhere "home" with just a device and an internet connection. That’s why I now identify as a global citizen. Through the internet, I aim to share my experiences, ask questions, learn from the tech community, and contribute to global problem-solving.

I also want to use this platform to challenge stereotypes. Too often, people are surprised to learn that Africans are using advanced technology, as if it’s something we only access after leaving the continent. On my first day at school, a colleague asked if I had ever used a computer before coming to Europe. This kind of ignorance fuels my determination to highlight Africa’s rapidly growing role in the global tech ecosystem.

In my next post, I will reflect on what it means to be an African immigrant in tech, especially in Europe, and the unique experiences, challenges, and opportunities that come with it.

To young developers: embrace your environment, but never let it confine you. Learn everything you can, and above all, don’t settle into your comfort zone.