Hello World!

Hello World! — in programming, these are words that signal something is awake and ready. This is mine. An introduction to who I am, what I’ve spent 23 years learning, and why this blog exists.

My name is Eonio. It comes from the ancient Greek Aionios (αἰώνιος) — meaning eternal, timeless, or of the ages. It is not a common name, which I’ve always taken as a quiet prompt to think in longer time horizons than the current sprint. My work is at the intersection of engineering leadership, digital transformation, and AI strategy — and my mission is straightforward: bridge the gap between what cutting-edge AI can do today and the measurable business value that enterprise organisations are actually capturing from it. That gap is wide, and closing it is the most interesting engineering problem of this decade.

Twenty-three years of building things

I wrote my first production code when the mobile market was still working out what it was — low-level C++, no GPU, memory constraints that forced a kind of disciplined minimalism I still carry. From there I founded MobRadio and GoMobie, two technology companies that taught me what shipping under pressure actually costs and what it produces. Some bets paid off in ways I didn’t predict; others failed instructively. Both were worth it.

I spent time in academia as a Professor of Game Development, which remains one of the best debugging tools I’ve ever used for my own thinking. Teaching forces you to articulate why something works, not just that it does. The gaps in your understanding become visible the moment a student asks a question you assumed was obvious.

From there, the trajectory moved into enterprise: larger systems, larger teams, and the kind of complexity that doesn’t care how fast you can type. The problems shifted from “how do I build this?” to “how do I build an organisation that can build this, sustainably, at scale?”

What I’ve shipped at scale

At enterprise level, the work gets more concrete — and the numbers start to matter. I redesigned cloud infrastructure that cut costs by 60% without sacrificing performance or reliability. I drove enterprise GenAI adoption before it was a safe boardroom decision, which meant building the internal case, managing the risk, and delivering the pipeline before the executives had a word for what we were doing.

Currently I’m at ASML — the company that builds the machines that manufacture the chips that power the world — leading AI Integration and CI/CD automation using autonomous agents across the engineering pipeline. It is a precision environment. Every architectural decision here has weight. That accountability sharpens the thinking.

How I think about engineering now

The most important shift in my thinking over the last few years is this: the bottleneck in software engineering is no longer execution — it’s intent.

Teams can ship faster than ever. AI tools have collapsed the cost of generating code to near-zero. What remains scarce is the quality of the upstream decisions: the architecture, the specification, the reasoning about trade-offs. The teams that will compound over the next decade are the ones that invest there.

My approach has three pillars:

Spec-driven development — write proposals, designs, and formal specifications before any code is generated. These documents become the authoritative source of truth for both humans and AI. The AI doesn’t replace the architect; it executes on what the architect has already decided, at throughput no human team can match. This blog was built this way. Every component, every page, every data model was specified first and generated second.

Autonomous agents as first-class contributors — AI agents that understand the spec, can generate conforming implementations, validate decisions against requirements, and close feedback loops without manual intervention. Not copilots. Contributors.

Scaling human potential — the goal of automation is never to reduce engineers. It’s to eliminate everything that prevents them from doing their best work. Freed from mechanical execution, engineering teams can operate at the strategic layer. That’s where the compounding happens.

What you’ll find here

This blog is written for CTOs, VPs of Engineering, and senior engineers who are serious about building high-performance teams and navigating the AI transition with both technical depth and strategic clarity. The content organises around three pillars:

• AI-Assisted Engineering — GenAI, autonomous agents, and agentic tooling applied to real engineering pipelines. Not demos. Decisions, architectures, and results.
• Software Architecture — cloud-native systems, spec-driven design, and the structural choices that outlast the code implementing them.
• Team & Org Transformation — how to scale engineering capability without scaling headcount, through automation, culture, and AI-augmented workflows.

I am not interested in tutorials for their own sake. Every post here is about reasoning and trade-offs — the decisions that weren’t obvious until they were yours to make. Browse the full archive, explore by category, or subscribe via RSS.

A final note

I live and work in Eindhoven, in the south of the Netherlands — a city that has quietly become one of Europe’s most important technology corridors. I’m learning Dutch, slowly. I compete in IPSC shooting, which teaches composure under pressure in a way that code reviews never quite managed. And I’m pursuing an Executive MBA, because I’ve learned that the best technical strategy is worthless without the business acumen to execute it organisationally.

Αἰώνιος. Think in longer time horizons than the current sprint.

Engines on, let’s roll!