Architecture diagrams can explain what a system looks like, but they rarely explain how teams should evolve it safely. Python systems often grow through rapid iteration, integration needs, and team-specific decisions, and over time the challenge becomes less about drawing the right diagram and more about creating governance that helps people make better changes. This talk reframes software architecture as a living decision system, built around decision records, ownership boundaries, integration contracts, stakeholder alignment, and change readiness.
Code is cheaper than it's ever been, and it will never be this expensive again. Every few decades a technology flips the table on a profession, and software engineering is having that moment right now. The noise around it makes the moment hard to read, and most developers either haven't tried these tools at all or got slop and quit.
I spent the last year learning, building, and refining damn near everything with Claude Code, to unbelievable success. This is what survived contact with the work. The principles that held no matter which model was ahead that week, the tools I run on anything worth doing properly, and an honest accounting of which customizations earned their keep and which ones only ate my evenings. This presentation is for both of those people, plus anyone already using these tools who wants to compare notes.
During this presentation attendees will:
Learn where AI adoption lands in software engineering's long history of abstraction, and why this shift isn't the one the CASE tools promised
See a repeatable workflow that produces code they understand, and the guardrails that make an agent's output worth shipping
Leave knowing why cheap code makes them worth more, not less
Learn how to maintain code quality without sacrificing performance. This presentation explores SAST, SCAT, and SCA concepts, then introduces modern tools like Ruff and Pyright that make formatting, linting, and type checking simple and almost instantaneous.