Autumn Nash
I work at the intersection of Linux, open source, security, infrastructure and software delivery. Senior Developer Relations Engineer @ Victoria Metrics
My work focuses on the systems that move software from upstream communities to production—from Linux distributions and release engineering to security, automation, CI/CD, and cloud infrastructure. I’m interested not just in how these systems are built, but in how the people and organizations around them make them work.
I’ve worked across engineering, security product management, solutions architecture, and developer education, giving me a perspective that spans both technical implementation and the decisions that shape it.
I’m particularly interested in the places where responsibility gets blurry: upstream and downstream, security and engineering, policy and implementation, developers and platform teams. Those handoffs are often where complexity—and risk—accumulates.
I contribute to open source, speak about Linux and security, and enjoy turning complicated engineering problems into practical mental models that people can understand, apply, and build on.
Sessions
Now we can generate thousands of lines of code in seconds, yet much of the conversation around AI has focused on prompts, agents, and productivity. We're optimizing for speed while asking the wrong question.
As information becomes abundant and execution increasingly automated, what does it actually mean to become an excellent engineer?
This talk explores how AI is reshaping the skills that matter most—not by replacing engineering fundamentals, but by elevating them. As tools continue to evolve, engineering principles remain our foundation. Judgment, systems thinking, curiosity, mentorship, collaboration, and stewardship are becoming the qualities that distinguish exceptional engineers, and they're the skills we'll need to intentionally cultivate in ourselves and the next generation.
Drawing on lessons from open source, Linux engineering, and real-world AI workflows, we'll explore practical ways to use AI as a learning partner rather than a thinking replacement. We'll cover techniques such as creating effective AI context, reviewing AI-generated work, building project memory, and using AI to deepen understanding instead of bypassing it.
Attendees will leave with practical engineering techniques they can apply immediately, a framework for building long-term engineering judgment, and a renewed perspective on how to invest in themselves, mentor others, and help shape the future of our profession.
It's a question almost every Linux user, developer, or platform engineer has asked. Behind that seemingly simple question lies one of the most important, and least understood, engineering tradeoffs.
Every application, container, and cloud workload depends on software that has been packaged, tested, maintained, and released by a Linux distribution. Yet most engineers never see the work required to transform upstream source code into software that is stable enough to trust in production. Every package update must balance security, compatibility, regression risk, reproducibility, dependency management, architecture support, release criteria, and long-term maintenance. What appears to be "slow" is often deliberate engineering designed to reduce risk for millions of users.
In this session, we'll follow a package from its upstream release to its arrival in a Linux distribution, exposing the decisions, tradeoffs, and engineering practices that happen along the way. We'll explore why maintainers backport fixes instead of always upgrading, why regression prevention often outweighs feature velocity, and how release engineering quietly protects the software ecosystem that nearly every modern application depends on.
Whether you build applications, manage infrastructure, contribute to open source, or operate production systems, you'll leave with a practical mental model for understanding how Linux software reaches your systems, and a deeper appreciation for the engineering judgment required to balance innovation, stability, and trust at scale.
Linux distributions aren't slow. They're deliberate, because reliability is built one engineering decision at a time.