What are you coding?

[SharkyUK]

Those books are about £7 on ebay now (the gems ones), I might pick a few up just for nostalgia

Go for it! One of my favourites, not shown in the photo, is the Graphics Programming Black Book by Michael Abrash. I'm not sure how easy it is to grab a copy these days but I spent hours reading and dissecting that one. Last time I checked, I found copies selling for upwards of 150.00 GBP! I'm holding on to my copy! I believe the source code for the book is hosted in a github repo online and that there is a downloadable ebook version.

EDIT: https://www.jagregory.com/abrash-black-book/

 

[Rroff]

You also don't need to go to 27 layers of abstraction, which seemed to be a common thing some years ago. Again, this is a misuse - rather than a flaw - of OOP. In reality, a lot of modern software development uses a mixture of paradigms. It's not necessarily a case of one versus the other. A modern software programme might use OOP for domain modeling/system architecture, functional concepts for data transformations/state management, and procedural code in other places.

I think this is one of the issues - abstraction and OOP for the sake of OOP rather than it being a benefit.

Personally I massively utilise C style structs rather than classes where I can - in my opinion it makes for cleaner, easier to read, easier to optimise code which can be ported to other platforms or alternative libraries, etc. relatively easily if required.

 

[SharkyUK]

I think this is one of the issues - abstraction and OOP for the sake of OOP rather than it being a benefit.

Personally I massively utilise C style structs rather than classes where I can - in my opinion it makes for cleaner, easier to read, easier to optimise code which can be ported to other platforms or alternative libraries, etc. relatively easily if required.

Yes, I totally agree. There was/is a lot of time where OOP is being used to tick boxes and introduces levels of unnecessary abstraction and complexity (when there is simply no need).

That's one of the things I love about coding; one shoe size does NOT fit all.

Personally, I use OOP a lot but that has largely been guided by the projects I have worked on. My personal stuff is a mixture of hacks, paradigms, and bugs. Lots and lots of bugs.