I've always been "good with computers", or so my family would say. Growing up with technology from the ZX Spectrum days through to our first IBM-compatible Amstrad PC, I was the kid who couldn't resist tinkering to see how things worked. More often than not, this meant breaking things first, which gave me plenty of practice at fixing problems before anyone noticed!
This early curiosity led to helping teachers with school computers and becoming the go-to person for neighbours' tech troubles. One particularly memorable case involved a neighbour baffled by their sluggish computer: it turned out the kids had installed Limewire without understanding the risks, and the system was riddled with viruses. These experiences taught me not just technical troubleshooting, but the importance of being diplomatic about root causes and educating people about potential risks.
Starting university in 2000 to study Computer Science opened my eyes to the broader world of computing beyond just troubleshooting PCs. I was exposed to object-oriented programming, robotics, and artificial intelligence; areas that gave me a much deeper understanding of how software and systems could work together. This academic foundation proved invaluable for building the theoretical knowledge that would underpin my practical skills. However, it was a nasty encounter with a network worm during my time there that prompted me to explore alternatives to Windows, which is how I discovered Linux and opened up a whole new world of possibilities.
My professional journey began in 2005 with my first proper IT role, initially as a software developer before moving into system and network administration at an international organisation. There, I helped migrate European data centre operations and built new hosting infrastructure using Solaris on x86_64 hardware; right when Sun was embracing the more popular architecture.
The real learning came working with smaller companies, including a brief stint at a network startup (sadly, it didn't survive) and then at Headshift, where everything clicked into place. I modernised their network and hosting infrastructure, oversaw an office move, and learned the hard way about spanning-tree protocol (thanks to a colleague's creative VOIP phone cabling)! I designed an implemented a robust hosting environment using a combination of CentOS, the Xen hypervisor and iSCSI storage for internal and client projects. This is where I truly cut my teeth in DevOps, supporting development teams and ensuring smooth, rapid releases.
We were early adopters of AWS, and I was instrumental in helping one of our clients migrate from traditional co-located infrastructure to a scalable, robust setup using EC2 and RDS, managed with Chef. This experience cemented my understanding of cloud computing's transformative potential.
By 2014, I had built a solid reputation among colleagues who were starting their own ventures or joining other organizations. When they began reaching out for help with their infrastructure challenges, it became clear there was an opportunity to formalize what I'd been doing informally. That's when I founded Aztek Native Ltd.
The name reflects our approach: we're native to the technology landscape, understanding it from the ground up, with the precision and attention to detail that "Aztek" suggests. Over the past decade, we've helped organizations of all sizes and industries optimize their infrastructure and workflows, keeping costs down while accelerating business operations – never compromising on security and reliability.
What started as one person's passion for understanding how things work has evolved into comprehensive IT solutions for businesses ranging from small startups to established enterprises. Whether it's infrastructure management (cloud-based or on-premises), automation, disaster recovery, business continuity planning, software development, network security, or IT project management, we bring that same hands-on curiosity and problem-solving approach to every client challenge.
The core philosophy remains unchanged: understand the technology deeply, anticipate what can go wrong, and always keep the human element in mind when implementing solutions.