Over the three decades, I've been on an everlasting quest to try to find the sweet spot in writing maintainable code that is properly covered by tests. I've been practicing Test Driven Development for the last 15 years and have experienced first-hand how easy it is to shoot yourself in your own feet. The same can be said about coding standards, the principles of object-oriented programming, SOLID and all the other acronyms that are so popular in our profession. So it's time to bring some sanity and common sense in all of that.

What will you learn?
• The basics of writing clean code without being dogmatic about it
• The traits of maintainable codebases
• Internal vs external quality
• Architecture styles and the impact on code quality
• Code documentation or not
• The ideal (unit) test
• What TDD means in reality
• Finding the right scope of testing
* Best practices for writing maintainable tests

How interactive is it?
I'm planning to make it as interactive and fun as possible. The day will be a mixture of me talking and you analyzing, discussing, refactoring and writing some unit tests. Most of the code examples will come from my own open-source project www.fluentassertions.com, so for those that don't feel comfortable enough with C#, we'll mix and match attendees.