I Didn't Just Witness the Technology Revolutions — I Built Through Them
There is a strange privilege that comes with spending nearly two decades in technology.
You don’t just learn programming languages and frameworks.
If you stay curious long enough, you get to watch entire industries change.
You see computing move from desktops to pockets. You see physical devices become connected. You see people experiment with decentralized systems. You watch computers begin to understand the physical world through cameras and sensors. And now, you are watching software become increasingly capable of reasoning, creating, and working alongside humans.
Looking back at my own career, I realise that I have been fortunate enough to participate in several of these technology waves firsthand.
From iPhone development and mobile applications, to IoT, blockchain, AR/VR, cloud platforms, and now AI.
Each one felt like a different revolution at the time.
Together, they tell the story of how technology has changed — and how I have changed with it.
The Mobile Revolution — When the Computer Moved Into Our Pockets
Early in my career, I spent years building mobile applications, particularly for iOS.
At the time, the smartphone was still establishing itself as a computing platform.
The idea that a phone could become the primary computer for millions of people was still relatively new.
Developing for the iPhone felt fundamentally different from traditional software development.
You had a camera, accelerometer, touch interface, sensors and network connectivity — and soon, GPS — sitting inside a device that people carried everywhere.
The interaction model changed.
The constraints changed.
The possibilities changed.
I spent roughly eight years in the mobile development world, and it taught me something that has stayed with me throughout my career:
The most interesting technology is often not the technology itself, but what becomes possible because of it.
The iPhone wasn’t revolutionary simply because it was a powerful device.
It was revolutionary because developers could build entirely new experiences around it.
And that lesson would repeat itself many times.
IoT — When Software Started Touching the Physical World
The next wave that pulled my attention was IoT.
The fundamental idea was fascinating:
What happens when almost everything around us can communicate?
Sensors could collect information.
Devices could transmit it.
Backend systems could process it.
Applications could turn that information into something useful.
Suddenly, software wasn’t confined to a screen.
It was interacting with machines, environments and physical processes.
This required a different way of thinking.
Mobile development had been largely about the interaction between a human and a device.
IoT introduced a much larger ecosystem:
Device → Network → Cloud → Data → Application → Action
Reliability, connectivity, device management, data processing and distributed systems became just as important as the user interface.
It was another step toward the world we live in today — a world where software increasingly sits underneath everything.
Blockchain — Rethinking Trust
Then came blockchain.
Like many technologists, I was fascinated by the idea that we could build systems where trust didn’t necessarily have to come from a central authority.
I explored blockchain technologies and decentralized applications, including smart contracts and Web3 concepts.
There was plenty of hype around blockchain.
But underneath the hype was a genuinely interesting technological idea:
Can software create mechanisms for trust, ownership and coordination without relying entirely on traditional intermediaries?
Whether or not every blockchain use case ultimately succeeded, the technology introduced new ways of thinking about distributed systems, digital ownership, cryptography and decentralized applications.
It also reinforced another lesson for me:
Technology waves don’t always replace the previous wave. They add another layer to the technology landscape.
AR/VR — When the Interface Became the World
My exploration of AR and VR was another fascinating shift.
For decades, computing had largely been about interacting with rectangles:
A monitor.
A phone.
A browser.
A screen.
AR and VR challenged that model.
Instead of bringing information onto a screen, what if we brought digital information into the environment itself?
What if the interface became the world around you?
Building and experimenting with AR/VR made me think differently about interaction, spatial computing and the relationship between humans and machines.
Once again, the technology wasn’t interesting merely because it was new.
It was interesting because it changed the question:
Instead of asking, “How do I put information on a screen?”
we could ask,
“How should humans interact with digital information at all?”
Cloud and Platform Engineering — Building the Infrastructure Behind the Revolution
As my career progressed, my focus moved increasingly toward backend engineering, cloud infrastructure, DevOps and platform engineering.
This was another major transformation.
Applications were no longer simply deployed onto physical servers.
Cloud computing changed the economics and architecture of software.
Containers, Kubernetes, infrastructure as code, CI/CD, managed services, APIs, serverless architectures and cloud-native platforms became increasingly important.
I found myself working not only on applications but also on the platforms that allowed other engineers to build and ship those applications.
That transition taught me something important about engineering maturity.
Early in my career, I was primarily concerned with:
“How do I build this feature?”
Later, the question became:
“How do I enable an entire team to build, deploy and operate software reliably?”
That was a significant shift in perspective.
And Then Came AI
And now we are here.
AI feels different.
Not because previous revolutions weren’t transformative, but because AI is beginning to change the nature of software development itself.
The previous waves gave software new capabilities:
- Mobile gave software mobility.
- IoT gave software access to the physical world.
- Blockchain introduced new models of trust and ownership.
- AR/VR introduced new ways of interacting with digital information.
- Cloud gave software unprecedented scalability and infrastructure flexibility.
AI is giving software something fundamentally different:
The ability to understand, generate, reason and assist.
And for someone who has spent years building software, this is particularly interesting.
I’m no longer just asking:
“What can I build with this technology?”
I’m increasingly asking:
“What happens to software engineering when software itself can help build software?”
I’ve been experimenting with AI-native development tools, coding assistants and agentic workflows, while also exploring how AI can be incorporated into real business processes.
The transition reminds me of the early days of mobile development.
There is excitement.
There is hype.
There are questionable use cases.
There are genuinely transformational ones.
And there is a lot that we simply don’t know yet.
But that uncertainty is exactly what makes it interesting.
The Common Thread
When I look back at these different technology waves, they initially appear unrelated.
iPhone development.
IoT.
Blockchain.
AR/VR.
Cloud.
AI.
But there is actually a common thread.
Each wave changed the boundary of what software could do.
- Mobile moved computing closer to the individual.
- IoT connected software to the physical world.
- Blockchain explored new models of trust and ownership.
- AR/VR changed how humans interact with digital environments.
- Cloud transformed how software could be built and operated at scale.
- AI is changing how software can understand information and collaborate with humans.
And throughout all of these changes, one thing has remained constant:
The technology changes. The ability to adapt does not.
What 18 Years in Technology Has Taught Me
If there is one lesson I have learned from moving across these technology waves, it is that betting your entire career on a particular technology is risky.
The technology you master today may become a commodity tomorrow.
Frameworks change.
Languages change.
Platforms change.
Architectures change.
Entire industries change.
But the ability to learn, understand fundamentals, experiment and adapt remains valuable.
I’ve gone from writing mobile applications to working with distributed systems, cloud platforms, infrastructure, emerging technologies and now AI.
The tools are completely different.
The underlying engineering mindset is surprisingly similar.
Understand the problem.
Understand the constraints.
Build something.
Learn from it.
Improve it.
Repeat.
The Next Revolution
I don’t know what the next major technology revolution will be.
Maybe it will be robotics.
Maybe spatial computing will finally reach its potential.
Maybe AI agents will fundamentally change how companies operate.
Maybe something we haven’t even named yet will emerge.
But after nearly two decades in technology, I’ve become comfortable with not knowing exactly what comes next.
In fact, I enjoy it.
Because I’ve learned that you don’t have to predict the future perfectly.
Sometimes, you just need to be willing to explore it.
I was fortunate to be there when the computer moved into our pockets.
Then when software started connecting to the physical world.
Then when developers experimented with decentralized applications and immersive computing.
Then when cloud became the foundation for modern software.
And now, as AI begins to reshape software itself, I find myself at another interesting starting point.
I don’t want to simply watch the next revolution happen.
I want to build through it.