CROSS FRAMEWORK
TRACK
Paul Ardeleanu
Principal Architect
Vonage, part of Ericsson
Paul is a Principal Architect at Vonage, working at the intersection of architecture, AI, and developer tooling, helping transform how developers interact with CPaaS and Network APIs. Having transitioned from managing Developer Relations teams to the central Architecture Team, he brings a unique perspective: understanding both the strategic vision required for enterprise architecture and the practical realities developers face daily.
His path in technology began with Fortran and a PhD in Computational Physics from the University of Lancashire, UK. Decades of hands-on programming experience since then have shaped his approach to architecting systems that serve developer needs. Paul remains active in the developer community through speaking engagements and writing, with a particular focus on JavaScript, Ruby, Swift and Rust.
Your Next Customer Is a Robot So... Who Are You Writing Docs and Building Tools For?
Session
It's 2am on a Tuesday morning, and an agent is perusing your internal documentation. Outside your company, another is deciding whether your SDK is easier to work with than competitors'. Neither will open a support ticket and, by the time you awake, both are gone and you never knew.
The agent isn't skimming but acting on what it reads, for a service it doesn't own and a team it won't notify. And it finds three of your six endpoints documented and tacitly concludes the other three don't work. It tries the CLI, gets back "Error: something went wrong", and stops: that sentence was all the context it had to correct itself with. So it tries your competitors.
We used to get away with this. Gaps in internal docs were covered by asking whoever wrote them; gaps in tooling by a human who could squint at an error and guess. An agent can't ask Dave, and it can't squint.
This talk is about writing docs for a reader that doesn't skim, and building tools for an operator that can't click.