4 ms·
I feel the same. Coming of age in the late 1990s OOP was all the rage and while I found a lot of it interesting and useful, it created a lot of its own problems
by kevstev 4y ago
I feel the same. Coming of age in the late 1990s OOP was all the rage and while I found a lot of it interesting and useful, it created a lot of its own problems and the solution was often just "more oop" in the form of design patterns and such. Meanwhile I always preferred composition over inheritance and templates made a lot more sense to me than crazy object hierarchies ever did.
I almost actually considered leaving programming in the mid 2000s but then I started seeing the tide slowly turn away from OOP, or at least I found voices that agreed that OOP is not the only answer and I felt a sense of relief. Then as latency became a more and more important thing in algo trading, it eventually fell out of favor almost entirely.
But yeah, OOP has a place but it really went overboard for awhile and there was jiggawatts of brainpower spent on trying to make it work when straight C or other approaches would have worked much better- and with much more grokable code!
- colechristensen 4y agoMine was more extreme... I basically stopped learning to program after hello world and simple math because there was all of this OO stuff and it was like "ok I can follow these examples but have no idea what any of this would possibly be for" and that was that for years.
- bowsamic 4y agoMy first solo experience was a VB.NET book with Car, SuperCar, Truck and all this stuff. Even at the time (I was very young) those laughably shallow examples stuck out as contrived and useless
- adamddev1 4y agoInteresting, I've been learning and doing almost everything with a functional or procedural style, but I've felt kind of guilty I don't understand OOP patterns enough, or don't know when I would want to use them. So I've been learning Smalltalk/Pharo and reading Smalltalk, Objects, and Design [1] because people say that's what OOP was really supposed to be. It's been interesting and enlightening in some ways, but I still feel like I'd rather do most things without OOP. Do you think it's still helpful or worth it to dig into all this for someone now? [1]: https://www.amazon.com/Smalltalk-Objects-Design-Chamond-Liu/dp/1583484906 https://www.amazon.com/Smalltalk-Objects-Design-Chamond-Liu/...
- bowsamic 4y agoYou should read Gang of Four imo. There are still a lot of very influential ones in there
- progre 4y ago"Read" GoF is not a thing I would do, just as I don't sit down and read a recipe book. Because GoF is kinda a recipe book for oop. I would skim it though, just to have a sense of what's in there.
- bowsamic 4y agoIt's not very long. Why not just read it and work through it? It isn't written like a recipe book, but even if it was, you should sit down and read your recipe books