Coming Back to Cloudoasis

For a long time, most of my writing lived on LinkedIn. That made sense at the time. LinkedIn gave me reach, conversations, visibility, and the opportunity to connect with professionals across industries, technologies, and leadership roles. Many of the ideas I shared there came from real experiences, long nights troubleshooting systems, leading transformations, handling outages, managing teams, and navigating the constant evolution of technology leadership.

But recently, I realised something.

I don’t want my ideas to live only inside social media feeds anymore.

I want to build something more permanent.

That’s one of the reasons I’m coming back to actively write on Cloudoasis.

This blog is not just another technology website. It is a reflection of how I think about technology, leadership, architecture, business resilience, AI, infrastructure, and the human side of IT. It is a place where I can share deeper thoughts, longer stories, lessons learned, failures, wins, and the reality behind leading technology in modern organisations.

And interestingly enough, one question keeps following me everywhere lately.

“How do you balance deep technical knowledge with leadership?”

I have been asked this question many times over the last few months, in interviews, customer meetings, mentoring sessions, conferences, and even casual conversations.

The honest answer?

I never saw them as separate things.

The Biggest Misunderstanding About Leadership in IT

Somewhere along the way, the industry created this strange idea that technical people eventually “graduate” into leadership and slowly stop being technical.

As if leadership and technical capability sit on opposite sides of the table.

I disagree with that completely.

In my experience, the best technology leaders are not the ones who abandoned technology.

They are the ones who learned how to translate technology into business outcomes.

There is a major difference.

I still love architecture diagrams.

I still enjoy troubleshooting.

I still get excited discussing identity systems, AI platforms, cloud strategy, networking, automation, Hyper-V, security, APIs, and modern infrastructure design.

I still spend time learning.

I still build things.

But the difference today is that I no longer look at technology only through the lens of “Does it work?”

I look at it through:

• Business impact
• Operational resilience
• Cost optimisation
• User experience
• Risk reduction
• Scalability
• Team capability
• Long-term sustainability

That shift changes everything.

Early in My Career, Technical Skill Was My Identity

Like many engineers, I built my confidence around technical capability.

If there was a difficult problem, I wanted to solve it.

If there was an outage, I wanted to jump in.

If something was broken, I wanted to understand every detail behind it.

And honestly, that mindset helped shape my career.

Working across consulting, enterprise environments, architecture roles, and leadership positions exposed me to incredible experiences. From government projects to enterprise infrastructure, from cloud transitions to security strategy, every environment taught me something valuable.

But eventually I learned an important lesson.

Being the smartest technical person in the room does not automatically make you a great leader.

A leader’s job is not to be the hero.

A leader’s job is to build an environment where the team can succeed without depending on a single hero.

That lesson changed the way I approach leadership forever.

Leadership Is Not About Stepping Away From Technology

One of the biggest mistakes organisations make is promoting strong technical people into leadership positions and then expecting them to disconnect from technology completely.

That creates leaders who:

• Lose touch with operational reality
• Depend entirely on vendors for direction
• Cannot challenge poor architectural decisions
• Struggle to mentor technical teams
• Become disconnected from engineering culture

I believe strong technology leadership requires enough technical depth to:

• Ask the right questions
• Understand risk properly
• Detect architectural weaknesses
• Guide strategy realistically
• Support engineering teams credibly
• Translate business goals into technical execution

The technical depth creates trust.

Teams can immediately tell whether a leader truly understands their world or only speaks management language.

And when your team trusts that you understand both the business pressure and the technical reality, conversations become healthier, faster, and more productive.

The Turning Point for Me

One of the biggest mindset shifts in my career happened when I stopped trying to prove technical expertise in every conversation.

Earlier in my career, I often felt the need to demonstrate knowledge constantly.

Over time, I realised leadership is less about proving capability and more about enabling capability in others.

That means:

• Mentoring instead of controlling
• Guiding instead of dominating
• Listening instead of always answering
• Building systems instead of building dependency

Ironically, the more leadership responsibility I took on, the more important technical credibility became.

Not because I needed to be the best engineer in the room.

But because modern businesses move too quickly for disconnected leadership.

Technology decisions today directly shape:

• Revenue
• Customer experience
• Security posture
• Operational continuity
• Competitive advantage

A technology leader who cannot understand the technical impact of decisions is effectively operating blind.

Why I Still Stay Hands-On

People are sometimes surprised that I still spend time building labs, testing platforms, working on AI integrations, exploring automation, reviewing architectures, and experimenting with infrastructure.

But for me, staying hands-on is not about ego.

It is about staying relevant.

Technology changes too fast for leaders to rely only on presentations and vendor summaries.

If you want to lead modern teams properly, you need to understand:

• What engineers are struggling with
• Where operational pain points exist
• Which technologies genuinely solve problems
• Which trends are mostly hype
• What implementation complexity actually looks like

The best conversations happen when leadership understands reality at ground level.

Not just strategy slides.

The Future Needs Hybrid Leaders

The future of technology leadership will increasingly belong to hybrid leaders.

People who can:

• Understand infrastructure and business
• Speak engineering and executive language
• Navigate AI and governance
• Balance innovation with operational stability
• Drive transformation without losing practicality

Pure management without technical understanding is becoming dangerous.

But pure technical capability without leadership maturity also creates limitations.

The real value sits in the balance.

And honestly, balancing both is still something I continue learning every day.