Presentation: Tweet"Introducing Change while Preserving Engineering Velocity"
Netflix moves fast and Engineering Tools is charged with enabling that velocity. With that goal in mind, we made a lot of tooling changes in the past year. But with change, comes cost. We are in the process of migrating several systems near and dear to our developers, including our version control system, deployment tool, and operating system for our AMIs. Our goal is to do this while minimazing impact on our customer teams, How did we do? What could we have done better? What aspects of Netflix's culture enabled this? And, most importantly, what can you take back to your own companies regarding the importance of making improvements while mitigating the tax on your teams?