With Kotlin, some of the object-oriented design patterns from The Gang of Four - no longer need to be applied. The GoF design patterns were initially introduced to address issues due to technical limitations in the context of C++ & Java. In contrast - Kotlin was designed ground-up keeping these same problems and limitations in mind - so much so that Kotlin has solved the same issues by using the language rather than relying on developers to implement a pattern after the fact.

This "myth-buster-esque" presentation will take a closer look at some of the creational, structural and behavioural design patterns from the GoF book. Specifically, we will be deconstructing the factory, builder, and prototype patterns; destructuring adapter, proxy, and decorator patterns; breaking apart the visitor and mediator patterns. There are many more patterns to go through but these are the most controversial ones we have the time for.

This presentation will challenge the orthodoxy and deep dive into the "why". For each pattern, we will be taking a look at what the problem is first. Only then, we will take a look at how the GoF design pattern intends to address the said problem. Afterwards, we will critique the pattern, assess the need for such a pattern and discuss whether this problem even exists in the context of Kotlin.

In the absence of the need for these design patterns, we can finally lay these chapters from the GoF book to rest. If you have already known these patterns in the past, this presentation will convince you that you don't have to apply them anymore. If you didn't already know the patterns, then this presentation will convince you that you don't have to know them anymore. These patterns are a vestigial of the past that we can look back and learn from for the future.