▶ Watch ↗AI Engineer World's Fair 202514:40
Conference affiliation: Temporal · 2025
Mason Egger is a senior solutions architect at Temporal Technologies and president of the PyTexas Foundation. A former site reliability engineer, developer advocate, and curriculum developer, he teaches developers how distributed applications recover from failure. His work on AI agents starts with a practical observation: model calls and tool calls cross networks, so agents inherit the same interrupted processes, unavailable services, and state-management problems as other distributed systems.
Mason began using Python in 2013 while building a college Django application. He worked as a software developer at Forcepoint and later as a site reliability engineer at Vrbo, supporting production infrastructure and encouraging Python adoption. In his architectural talks, he draws on the operational consequences of mishandled queues: even an application with little business logic can cause a large outage through the infrastructure surrounding it.
He joined DigitalOcean in 2019 and became a senior developer advocate focused on cloud infrastructure, distributed systems, and Python. His work included maintaining DigitalOcean’s Terraform provider and teaching developers to provision production infrastructure with Terraform.
In 2022, Mason joined Gretel as lead developer advocate, helping establish its developer-relations practice and demonstrating how synthetic text generation can support machine-learning applications. He moved to Temporal in 2023 as a senior technical curriculum developer, creating courses, workshops, and code samples. He subsequently worked in developer advocacy before moving into solutions architecture, where he helps customers design and implement durable execution systems. His own description of his work puts teaching at its center: engineering, educational content, and community organizing are all parts of his practice.
In Events are the Wrong Abstraction for Your AI Agents, Mason questions how much machinery developers must maintain around the application they want to write. An agent architecture can accumulate message buses, dead-letter queues, cleanup jobs, local caches, and recovery logic until coordinating execution becomes more complicated than the underlying task.
His criticism turns on a distinction between runtime independence and design-time coupling. Services may continue running when another service goes offline, yet remain dependent on its event formats. A producer can have consumers its maintainers do not know about; changing a message can therefore break downstream applications unexpectedly. Meanwhile, following a business operation may require searching across services, each maintaining part of the state and handling its own failure cases.
Mason acknowledges that event-driven architectures work. His argument concerns which abstraction developers should work with. Temporal still uses events underneath, but exposes workflow logic in code while the platform handles execution history, timers, and retries. His durable Python agent tutorial applies this approach to an agent loop: completed model and tool results can be retained so recovery does not require starting the entire task again.
A joint workshop with Keycard’s Kim Maida made that distinction visible. Mason stopped a Python worker after an expense workflow had debited a ledger, while a timer simulated waiting for human input. Temporal’s execution history retained the completed debit result while the worker was offline. Restarting the worker reconstructed the workflow’s state and allowed settlement to finish without repeating the completed debit or making additional model calls. The example explained what preserving progress means: recovery reuses work already completed rather than paying to perform it again.
The workshop also separated two concerns that can otherwise collide: retaining results for recovery and keeping credentials out of that retained history. Mason explicitly credited the Keycard team with building the Temporal interceptor that obtained credentials when an Activity executed. He demonstrated the recorded debit and settlement results, then ran a Python check that found no JSON Web Token material in the execution history. For sensitive application results that do need to be retained, he described a separate option: encrypting payloads with keys controlled by the application’s operators. Keeping a credential out of history and encrypting a stored result solve different problems.
Mason’s writing also examines how he uses AI to build software. In How I Actually Use the Damn Thing, his Brainstorm, Plan, Execute approach separates developing a specification from planning implementation and carrying it out incrementally. Human review, tests, bounded tasks, and persistent session summaries provide a way to continue substantial work across conversations without asking the model to resolve the whole project in one pass.
His community work has developed alongside his engineering and teaching roles. Mason began speaking at Python conferences in 2019, helped move PyTexas online in 2020, and chaired its return to an in-person conference in 2022, when he became foundation president. He also helped found the PyTexas Meetup. He received a Python Software Foundation Community Service Award in 2024 and became a PSF Fellow in October 2025.
▶ Watch ↗AI Engineer World's Fair 202514:40
▶ Watch ↗52:36
Loading more talks and highlights…