Aaron Ardiri
Technology. Entrepreneurship. Experience.
I have spent more than three decades working with technology, from the early days of personal and handheld computing through to modern distributed systems, embedded devices, cybersecurity and artificial intelligence.
Along the way, I have written software, built products, founded companies, led engineering teams and worked with organizations of all sizes, from small startups to multinational technology companies.
Curiosity has always been the starting point.
My career has rarely followed a conventional path. What began as a fascination with understanding how computers worked developed into a lifelong interest in building things, solving difficult problems and exploring what technology makes possible. Some of that work has been commercial, some experimental, and some undertaken simply because I wanted to understand something better.
Over the years, I have learned that the hardest challenges in technology are not always technical. Architecture, complexity, communication, business realities and the decisions people make around technology often determine whether an idea becomes a successful product or an expensive lesson.
Today, I continue to work hands-on with technology while also providing independent strategic and technical advisory services through Aaron Ardiri AB. I enjoy working with people who are building something meaningful, particularly where practical engineering experience can help bring clarity to complicated decisions.
Experience is useful when it helps make better decisions.
Building software is one thing; keeping it useful, maintainable and aligned with the people who depend on it is another. I have worked on both sides of that challenge, as an engineer responsible for implementation and as a technology leader responsible for direction.
Through Aaron Ardiri AB, I offer independent advice on architecture, engineering practices, product direction and the practical realities of delivering complex systems. The aim is not to introduce more process for its own sake, but to help people see the important decisions more clearly.
Writing things down is another way of understanding them.
Writing has become an increasingly important part of my work. My books explore computing, algorithms, mobile networks and the experiences accumulated throughout my career. They reflect the same curiosity that first drew me into programming: understanding not just how something works, but why it works the way it does.
My autobiography looks back at the people, projects, decisions and unexpected turns behind that career. The technical books follow a different thread, taking complicated subjects apart and exploring the ideas beneath them.
Some things are worth preserving.
I have been fortunate to work through several generations of computing, from handheld devices and mobile platforms to embedded systems and connected products. Many of those platforms have disappeared, but the lessons learned from building for them remain relevant.
Preserving old development tools, source code and technical history is one way to make sure those experiences are not lost. I still enjoy exploring new technologies, but I also believe there is value in remembering how we arrived here.
Sharing what I have learned.
Speaking at conferences and working with developers around the world has been another important part of my career. Those conversations have often been as valuable as the presentations themselves, bringing together different perspectives on engineering, innovation and the realities of building products.
This website brings those interests together: my books and publications, professional work, technical projects and historical material from an industry that has changed enormously during my lifetime — and continues to change.
There is always something new to learn, something worth building, and occasionally something from the past worth preserving.