Structured programming. That's so 1970s, right? It was all about gotos (or not) and has no more relevance to current programming practice, with its exceptions, threads, object models, functional hand-me-downs and refactorings, than flared trousers, disco or punk. Or perhaps there is and always has been more to structured programming than this oversimplified view?

This session looks back at the thinking that motivated and informed structured programming, from "Go To Statement Considered Harmful" to block-structured code and its realisation in object orientation, from formal reasoning to design by contract, to look forward at its enduring implication for modern programmers, namely being able to understand and reason about the code they are looking at.