Leslie Lamport makes the case for separating the design details of what a program should do and how it should work from the business of writing code, and discusses how the design process should work.
Doug Hiebert questions conventional wisdom that is taken for granted when writing code, and presents alternatives by way of before-and-after examples.
Alex Papadimoulis attempts to define ugly code, how one can recognize it, providing advice on avoiding writing such code and refactoring old code to get rid of it.
Nat Pryce considers that we cannot write the perfect code because it is never fully prepared for the coming change, so he suggests embracing impermanence & continual imperfection.
Bill Pugh dissects three Java puzzlers and bug patterns, explaining how to fix them, what is lessons to be learned, and how to avoid such coding mistakes.
Robert C. Martin on writing good code starting with a bad code example, then addressing many topics like: Boy Scout rule, functions, arguments, craftsmanship, TDD, engineering, certification, etc.
Jeremy D. Miller shares lessons learned while developing a project over 5 years. He talks about his mistakes, what to avoid and how to design, code and test better.