The best part that you are reading my blog is that I don't need to convince you with tons of resources like a dirty trickster to follow me. The resources I share with you are the best roadmaps for programming languages I found, now in 2024. Those are my personal preferences, and here are not all the language programming, only the ones I'm interested in according to my career, but I'm sure you will find them useful.

I must confess I'm not a very big fan of all products related with Jetbrains. All because its ecosystem is based on Java, and as a senior developer, we all hate Java. 🤣

I'm going to tell you a story.

One day, at my grandmother’s house, my father brought a device that was connected to the TV. It was a ZX Spectrum 48k. After plugging it in and watching them load the cassette tapes (with a sound that was a little weird) and playing on the TV, I fell in love with this new machine. I had already seen an Atari with the Pong, but this was another level.

Finally, we reach the last principle of the SOLID series. The Dependency Inversion Principle is the most complex of all, but I'll try to explain it in a simple way.

We are almost ending the series of articles about the SOLID principles. Here you have a brief explanation of each principle to review them:

In the noble art of coding, you should remember the SOLID principles always. Sometimes, I forget some of them, so here is a brief explanation of each principle:

Today, let's focus on the Open/Closed Principle.

---

First of all, here you have the four principles of SOLID:

In the noble art of coding, you should remember the SOLID principles always. Here is a brief explanation of each principle:

Today I was asked this question in a job interview, and I found it to be a very simple way to explain dependency injection. Here's the explanation I gave, a bit more detailed (I'm sure it blew my interviewer's mind):