Even if you already know some smells and refactoring, deliberate practice on specific exercises will up your game. In this hands on session, you will practise recognising different smells, learn a vocabulary of smells and learn how to make code less smelly with specific refactorings.
You’ll receive a free deck of refactoring cards and we'll work through a small piece of smelly code, identify its code smells and refactor to let its intentions shine through.
In case you are not familiar with code smells:
Often, you feel there are some things just not right with the code you’re currently working with. It is not always clear what exactly the problem is, but you can see some indicators of underlying problems. Many years ago, extreme programming founder and agile pioneer Kent Beck coined the term ‘code smell’ for these indicators: a code smell is a symptom of something that’s probably not right in code or in the design, even though the root cause might not be immediately apparent.
Different code smells have names like ‘comments’ or ‘long method’. This provides you and your team members a language to talk about code quality. To reduce smells in code, we apply refactorings in small steps (refactoring = improving the design of code without changing its behaviour). Often after applying a refactoring we uncover new smells.
Smells and refactoring cards let you quickly learn an extended refactoring vocabulary. The cards and vocabulary make it it easier to tackle larger design changes by a series of smaller refactorings while communicating your ideas with your colleagues.
Willem is a software developer and consultant, always looking for better and more fun ways to develop software, and helping others do the same. He's based in Bath and is a partner at QWAN.
Rob is a developer and consultant at QWAN.
To buy tickets to see this fantastic talk, and many others like it head over to our ticket page.