My journey on studying design patterns

I was advised to learn design patterns. The first thing I was taught about Spring Boot was “Dependency Injection”. I thought, I gotta learn these things so I earn the right to start having imposter syndrome as an OOP programmer.

I tried out 3 different books on GoF Design Patterns. I deliberately picked materials that have “real life examples”, because I knew I would not get the real world usage of cats and dogs. One of the materials was language agnostic, and written in more recent years because I have a bias for more contemporary stuff (evident in my movie and dance choices ;-))

The learning dragged out for at least half a year. I wanted to learn Kotlin at the same time but the language itself solved a bunch of problems. They also didn’t seem to give extra insights on how I could better design code at work. I ended up not understanding why I was studying them.

In one of my procrastination study sessions, I came across POODR and decided to give it a go as it was included in my O’Reilly subscription. It was the winner. [More on why next time!]

Whilst looking up Dependency Injection because James Ward and Bruce Eckel had a whole episode about Dependency Injection for Happy Path Programming podcast (oh so I wasn’t the only person not knowing what it is?!), I came across this:

So what am I doing now? POODR-ing.

Stay tuned.