This month we welcome author and multiple conference speaker Peter Hilton to give a talk on how developers can benefit from the untapped resource that is literature. We also hear from software craftsman Adam Kosiński, who will speak about fine tuning how we build tests.
Developers can get better at their craft by learning from the great writers who mastered theirs. Writing software isn’t the same as writing a novel, but there are parallels. Besides, advice from writers is better because writers have been struggling with their craft for many centuries, not just a few decades. It’s better-written as well. This talk shares great writers’ best advice for coders: Stephen King on refactoring, Anne Rice on development hardware, Hemingway on modelling with personas, and Neil Gaiman on everything.
Peter Hilton is a software developer, writer, speaker, trainer, and musician. Peter’s professional interests are web application development, functional design, agile software development and project management. His speciality is database-backed intranet web application architecture, design and build. He currently builds web applications using Scala, Play Framework and Slick. Peter has presented at several European developer conferences, co-authored ‘Play for Scala’ (Manning Publications) and is a Typesafe certified trainer for ‘Fast Track to Play with Scala’.
By now hopefully most of the developers know tests are worth writing. Unfortunately, sometimes their quality leaves a lot to be desired. Tests produced are tightly coupled, testing wrong things with wrong set of assertions.
There are many discussions addressing the questions like "What to test" and "How to test". But there is one equally important - "How to write test someone else can read". While there is no tool on the world that would do the former for you, the latter can be vastly improved with right set of techniques, tricks and libraries. If we are committing to writing tests, we might as well get the most of it.
That is what this talk will be about: ideas and patterns to produce clean, readable and developer-friendly tests. We will look deep into technical details, some of which include: patterns for building your test objects, prettifying test output or defining descriptive assertions.
Adam is a software developer at PayPoint, journeyman on objective, functional, mobile and any other code worth writing. Keenly interested in principles behind programming and curious why people do what they do and write code they write.