By Marco Luizinho, Team Lead here at Entelect

That’s one of the reasons I like to write and why I love to read the perspectives of others. Don't get me wrong, theory is invaluable, but theory alone doesn’t account for the messy, unpredictable, and deeply human aspects of our work. What’s written in books doesn’t always map neatly in practice. Two organizations that seem almost identical on paper, can operate in wildly different ways. The company size, the industry, the culture, team sizes, organisational hierarchies and even the personalities on the team, are all factors that create an infinite number of variables and possibilities.

For example, two teams with the same goal, say, improving deployment frequency might take vastly different paths. One might succeed by implementing continuous integration and continuous delivery (CI/CD) pipelines, while another might focus on team communication and process alignment. Both are valid approaches, but their success depends on the nuances of their context.

This is why it’s so important to seek out diverse perspectives. Asking, listening to or reading about others’ experiences opens the door to solutions you might not have considered. A story about a team that adopted a new code review process or restructured their standups might spark an idea for your own team, even if it doesn’t immediately seem relevant. Sometimes, the lessons we learn don’t click until we face a similar challenge down the road.

The Art of Connecting the Dots

I like to think of this process as connecting the dots from Steve Jobs' famous "You can't connect the dots looking forward; you can only connect them looking backwards" speech. Every book you read, conversation you have, or article you come across adds a new dot to your mental map.

The more dots you have, the more opportunities you’ll have to draw connections. Maybe you’ll find inspiration for improving sprint planning from an article on leadership psychology. Or perhaps a podcast about agile transformations will prompt you to rethink how your teams handle technical debt.

One of my own "lightbulb" moments came when I read about the concept of psychological safety in teams. It wasn’t an immediate “a-ha” moment, at the time, my focus was on technical challenges. But months later, when I noticed a lack of collaboration in one of my teams, that concept resurfaced. I realized the issue wasn’t technical, it was cultural. By fostering psychological safety, the team’s dynamics improved, and the technical issues started resolving themselves. (What really happened I guess was that once people felt safe, respected and appreciated, they started applying themselves and their skills more).

Broadening Your Toolkit

Exposure to different perspectives equips you with a broad set of tools. Not every idea will be applicable to your current situation, and that’s okay. Some lessons will feel like a perfect fit, while others will be like tools waiting in your toolbox for the right moment. But the key is to keep adding to that toolbox and occasionally remind yourself of what you have in your toolbox (bringing things front of mind).

For managers and leaders, this practice is even more critical. Developers look to us not just for direction but for inspiration. Our ability to draw on varied experiences and solutions directly impacts our teams’ success. And for developers, exposure to different perspectives helps build the adaptability that’s so crucial in today’s tech landscape.

Sharing Is Building

Writing and sharing our own experiences can be just as important as consuming others’. Every time I share a story or insight, I’m not just reflecting on my own journey. I’m also hopefully contributing a new dot to someone else’s map. The beauty of our industry lies in its collaborative spirit, when we share what we’ve learned, we all grow.

Just today, a junior developer in one of my teams approached me with an idea for a knowledge-sharing initiative he wanted to implement across our space. Moments like this remind me why I do what I do. There’s nothing quite like seeing someone step forward with not just a great idea, but also the enthusiasm and drive to make it happen. His excitement and vision inspired me to finally turn this two-week-old draft into a published article.

So, as you navigate your career in software, I encourage you to embrace this mindset. Read widely. Listen intently. Write thoughtfully. You never know when a story, yours or someone else’s will provide the key to unlocking a challenge or sparking an idea.

In the end, it’s not just about finding answers. It’s about staying curious, staying open, and staying connected to the diverse and ever-evolving world of software delivery.

 
"... There were no textbooks, so we had to write them.” - Katherine Johnson