If a developer changes a line of code, how long does it take for that code to run in their development cluster? L Körbes, an expert in Kubernetes development tooling, has seen the answers to that question vary between 1 second and 30 minutes. How can a dev get their team’s code to be on the former side, not the latter? In this talk, L discusses the many factors at play: container image layers, Dockerfile hacks, dependency caches, compiler caches, file watching, file syncing, where to compile code, remote vs. local dev clusters, considerations between dynamic and compiled languages, and more. The demo will start from the simplest possible setup, using a compiled and a dynamic language in parallel, and increasingly improve on it until the shortest possible iteration time is reached. The audience can expect an in-depth exploration that they can use to make development faster right away.