Maybe it’s just my experience, but Object-Oriented Programming seems like a default, most common paradigm of software engineering. The one typically thought to students, featured in online material and for some reason, spontaneously applied even by people that didn’t intend it.
I know how succumbing it is, and how great of an idea it seems on the surface. It took me years to break its spell, and understand clearly how horrible it is and why. Because of this perspective, I have a strong belief that it’s important that people understand what is wrong with OOP, and what they should do instead.
Many people discussed problems with OOP before, and I will provide a list of my favorite articles and videos at the end of this post. Before that, I’d like to give it my own take.
Data is more important than code…
Read in full here:
This thread was posted by one of our members via one of our news source trackers.
Awesome, I will add a note to this thread so I don’t forget: Which book clubs shall we start next? (I’ll start on it all around the time of our first birthday, which is on the 20th of this month - i’ll ping you both then!)
That book was such a pleasure to read! I kept thinking, “this is one of those books that I’ll have to get back to and give it a second read just to reinforce the ideas in my silly brain” – and I definitely will, once I’m done with the other eBooks that are on top of my seemingly unending to-read stack.
wait, am i reading it correctly?
