Programmers are used to their compilers catching tiny problems in their code. When you're a writer, it's harder to catch these problems. Wouldn't it be nice if you could run an error-checker on your dialogue? In this talk, we'll discuss how optimisation techniques from compiler design can be translated to narrative tools, like static analysis and control flow graph analysis, can be used to spot problems in your dialogue. For example, it's possible to prove that a certain branch of dialogue can never be reached because earlier decisions made by the player will always render that choice unavailable. Come and learn how to get started with these techniques, and how to use them in Yarn Spinner, the open source narrative design tool!