Monday 19th May, 2014
9:30am to 5:30pm
When you look for it there appears to be no shortage of technical wisdom on what makes for clear and robust code. The quantity and consistency of such wisdom can, however, often leave programmers swamped. This may, in part, help explain why so much of the advice is ignored in so much code. Ideally there should be common themes that can be found across the many different specific practices identified as great and good, principles and overarching guidelines that help to make sense of the details and contradictions.
This session offers a thirteen-point list of recommendations (zero through twelve) which can be applied out-of-the-box to reduce code size and complexity, acting as guidelines for new code, indicators for refactoring and opportunities for review and discussion. The short list has no ambition to be all that you needed to know about design but were afraid to ask, but it does offer an easily memorable and rewarding set of practices for anyone who wants to ask better questions of their code. This workshop will also allow plenty of opportunities for discussion.
Kevlin is an author, presenter and consultant on software development
Focusing on OO design, patterns, Agile development and software architecture. Kevlin has written on the subject of programming practice for many magazines and websites, including Better Software, The Register, C/C++ Users Journal, Application Development Advisor, Java Report, and Overload. He is a member of the IEEE Software Advisory Board. Kevlin is also co-author of two books on patterns, and editor of 97 Things Every Programmer Should Know. Over the years he has spoken at numerous conferences around the world, including ACCU, DevWeek, GOTO, Software Architect, OOPSLA and QCon.
Sign in to add slides, notes or videos to this session