Clean Code by Thomas Sundberg

Speaker Thomas Sundberg
Clean Code

What happens if you write something quick and dirty? What happens if you cut corners? You will most likely end up with a code base that is hard to read and hard to maintain. This is the definition of bad code and technical debt.

Is this a problem? Is bad code really an issue that you want to consider? Yes, if you plan to maintain and extend it to adapt to new or changing business requirements. Bad code is rotting code that gradually will slow you down until you grind to a halt. Can this be avoided? Yes, if you always strive for good testability and maintainability and thus end up with a clean code base.

I will discuss the concept of Clean Code in this presentation and introduce the concepts laid out in the books Clean Code by Robert C Martin, Working Effectively with Legacy Code by Michael Feathers and Refactoring by Martin Fowler.

Topics that will be covered are

  • Meaningful Names – why is naming so important?
  • Functions – how should they be written and which abstraction level should they contain?
  • Comments – why do you write comments?
  • Objects and Data Structures – which abstractions should we have?
  • Error Handling – checked or unchecked exceptions?
  • Unit Tests – how should they be written and what should they communicate?
  • Successive Refinement – how do we evolve our implementation?

Be prepared for a lot of code examples, some of them really bad, and suggestions on how to make them more readable. Readable but bad code can be fixed. Converting bad code to readable code is a good start, but it is not the end.


Clean Code, Legacy Code, Refactoring, Bad code, Simple design, Unit testing, Automation, Technical Excellence

Last Updated 28 Jan 09:16