Every AI initiative seems to start with the same assumption: we need to hire Python developers. New job specs, new budget, new team — while the engineers who have shipped and operated your production systems for the last decade are quietly told this one isn't for them.

That assumption is slow, expensive, and wrong.

Shipping a production agent is a systems problem, not a machine learning problem. The model sits behind an HTTP API. Everything on your side of that boundary is work your team already does well: structured data, retries and timeouts, concurrency, state, queues, authorisation, observability, and deployment. The hard parts of agentic AI are the parts your people have been solving for years — nobody has told them that yet.

In this session we build the case from the code up. I'll walk through a real agentic application and show how small the genuinely AI-specific surface actually is: an agent loop is a few hundred lines of ordinary control flow, tool calling is a JSON schema and a dispatch table, memory is data modelling, retrieval is search, and evaluation is testing with a fuzzier assert. We'll see the same patterns expressed in Go, C#, Java and TypeScript, because they are not language features — they are architecture. With a live demo, running on the stack it was written in.

I'll also be straight about where Python genuinely wins — training, fine-tuning, notebooks, the data science ecosystem — and how to tell whether you are actually doing that work or just assuming you have to.

For leaders: your AI capability gap is probably not a hiring problem. For engineers: you are already qualified.

Takeaways

- Why agentic AI is an integration and systems problem, not an ML one
- The anatomy of an agent loop, tool calling, memory and retrieval, in plain engineering terms and independent of language
- How to map those patterns onto the stack and skills your team already has
- An honest boundary: what Python is genuinely better at, and how to recognise when you really need it
- What to do on Monday morning instead of opening a requisition

Preferred duration: 45 minutes including Q&A. Can be delivered in 30 or 60 minutes on request.

Target audience: engineering leaders, architects and senior developers who are starting or evaluating AI initiatives. No machine learning background required.

Level: intermediate.

Technical requirements: my own laptop (USB-C / HDMI) and internet access for the live demo. A recorded fallback of the demo is always available.

Related delivery: a Go-specific version of this material, "How to write great agentic AI without python", has been accepted at {dev.talk} 2026. This session is the language-agnostic evolution of it, aimed at a broader audience.