Regardless of industry, programming language, or company size, change is a necessity in technology. We can’t effectively anticipate all future evolutions, but we can learn from past experiences to inform how to make our systems easier to change without over-engineering. The ability to safely and effectively deploy change at scale can be the difference in beating competitors to market, mitigating zero-day vulnerabilities, keeping developers happy, and ensuring customers have a reliable product.
Change is present every day in how we evolve our systems and release features. It is there when we decide to adopt a new technology or migrate systems from one solution to another. It’s also there when we need to rapidly address large-scale vulnerabilities at scale like we saw last year with log4j.
In this track, attendees will learn patterns and practices to help them architect systems and tooling with agility top of mind – enabling technology to keep up with the needs of the business while minimizing risk and technical debt
From this track
Adopting Continuous Delivery at Lyft
All organizations, regardless of size, need to be able to make rapid changes and improvements in their constantly growing systems. How can we handle all this change while maintaining a reliable product?

Tom Wanielista
Senior Staff Software Engineer @Lyft
Dark Side of DevOps
Topics like “you build it, you run it” and “shifting testing/security/data governance left” are popular: moving things to the earlier stages of software development, empowering engineers, shifting control definitely sounds good.

Mykyta Protsenko
Senior Software Engineer @Netflix
Crypto Agility: Risk Management For When Your Service Can Take Down Everyone
In May 2022 the White House released a National Security memorandum

Anvita Pandit
Senior Software Engineer @Google
Architecting for Change at Scale Presentation 4
Details coming soon.