Gotta love OOP

When i have multiple DAOs, sometimes i make a DAOFactory

you could ascribe this to any paradigm. A system is a network of dependencies is virtually any system that's non-trivial.

I could relate to this. Fml

That's called bad design and inexperienced programers. It's a tool like any other, use it wrong and you'll hurt yourself and others.

Ohh so it is not just me? Great to know... I thought I was fucking up all my designs 👍

I've actually seen worse from functional style programming and I would normally not think that such things would be possible.

OOP is love

ITT folks who don’t follow the S.O.L.I.D principle.

https://en.wikipedia.org/wiki/SOLID_(object-oriented_design)

So true, but still love OOP, I find it so natural... I'm maybe too chaotic

Yeah, it's a tool and that's fine. It's just that it tends to invite thinking a million miles ahead which can really hamper progress. Like: "I can just make this simple object but later on I might want to call it a different way and if I abstract it more, I can maybe reuse it later, and what if I want to inherit from it in this special way..."

That kind of thinking leads to a clusterfuck where you're trying oh so hard to follow the paradigm and design patterns instead of writing code that just does what it needs to do.

OOP has its uses, but don't get stuck thinking about design patterns. Just write the simplest thing that will work, you can always make it "nice" later.

Subhuman 😂

@mcalis code that works right now ALWAYS leads to the nightmare legacy code 90% of us here rant about. When civil engineers are building a bridge they have to confided just as many things but they don’t have the option of making it nice later... we need to be better

this is called "software engineering doesn't need a license, so any iliterate idiot can google 'java for nubz' and end up with this shit"

@rephiscorth and this is "that was a long ass quote like example, maybe we should have given this more time to see if we could have said something different, oh well"