The problem with Object-Oriented Programming

#neetcode #leetcode #python

[VoyivodaFTW]

I'm so glad I refused to jump on board the hype trains over the past 20 years. Functions and data structures will get you 90 percent of the way if you try not to get too cute

[NukeWalker]

If your code gets the job done clearly, efficiently and is easily maintainable and extensible, BUT violates some fancy principles... then take those principles and wipe your ass with them because you don't need them.

[asagiai]

I think this is also a problem.
People these are principles or guidelines, not Standards.
SOLID is not really solid at all.
I'm gonna say this, but OOP in itself is not bad.

Some people are just selling acronyms.

For me, when I code. I like my code that I can understand and can understand by others. (If not I also have comments and documentation that others can use)
I don't like that when I go back to a previous project. I have to rethink again what it is doing.
For me, that's the best principle.

[eyyfalon]

can someone tell me what the solid principle is for those who dont know

[planesrift]

It sounds like what corporations want, no?

[WhyOhWhy]

This happened to me last week. I started to reactor some code to use Dependency Injection. It took 3 times longer to do and meant, when I want to extend it, I would have to update 3 places instead of just 1.
I think applying SOLID is the ideal but isn't the rule.

[r-p]

What is the language used in the background?

[KamiKomplex]

General developers are in fact too dumb to code without following the systems, checks, reviews and guidelines to prevent them from making more work for the 10xers.