PRINCIPLE MISUNDERSTANDINGS

Many guidelines and tools shape our current designs, from the detail of the code to the broad brushstrokes of the architecture, from the roots of DDD to the expression of our paradigms. Architects, developers and tech leads often throw a number of principles, laws and guidelines into their discussions and markdowns.

Whether it's DRY code, Conway's law, the alphabet soup of SOLID principles, or old school classics like Information Hiding and the Separation of Concerns, there's a lot of advice out there to choose from. Some of it even makes sense. And some of it is well supported. But a lot of principles are misunderstood, misapplied or simply mistaken.

Following the philosophy that taking something apart and putting it back together again is a great way to learn about what matters, we will do this with a number of these common principles. During the day we'll look at (and take down) a few principles, highlighting the real lessons we can apply to the design of our systems — lessons supported by sound rationale rather than just strong opinions, and code examples will be in Java, JavaScript and other languages.