this post was submitted on 14 Nov 2024

70 points (88.9% liked)

Programmer Humor

32710 readers

267 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

[email protected]

TIFU by not using objects in my object-oriented programming coursework (lemmy.ca)

submitted 1 month ago by [email protected] to c/[email protected]

24 comments fedilink hide all child comments

top 24 comments

sorted by: hot top controversial new old

[–] LavenderDay3544 30 points 1 month ago* (last edited 1 month ago) (1 children)

I hate that schools basically teach students to over use classes for everything especially by using Java as a teaching language and then they get into the real world or grad school and we have to unteach them those terrible habits.

I'm so glad a lot of the newer languages (Rust, Go, Zig, C3, V) don't have classes in them at all.

[–] eager_eagle 12 points 1 month ago (1 children)

Tbh if the average grad school student overused object oriented stuff they would produce vastly better code than the status quo.

[–] LavenderDay3544 7 points 1 month ago (1 children)

I strongly disagree.

[–] eager_eagle 1 points 1 month ago* (last edited 1 month ago) (2 children)

I've seen plenty of grad student code, abundance of OOP concepts was never an issue. Complete lack of any structure on the other hand....

[–] [email protected] 2 points 1 month ago

You can't teach experience.

[–] [email protected] 1 points 1 month ago* (last edited 1 month ago)

Bad abstraction is worse than no abstraction

If the code is going to poorly organized, I'd prefer it to just be one single gigantic standalone script than some wrong and misleading arrangement of objects or functions that adds more complexity than they solve

[–] [email protected] 14 points 1 month ago

Strings are Objects, Doubles are Objects (that are than unboxed into primutives doubles)...

[–] HStone32 9 points 1 month ago (1 children)

I'm currently taking the very last CS class my major requires. I can't wait to leave OOP behind and focus on hardware completely.

[–] [email protected] 2 points 1 month ago (1 children)

where do you plan to go to start that off after school?

[–] HStone32 3 points 1 month ago

Either microcontrollers, operating systems, or something else involving RISC-V. That's still a ways off though.

[+] [email protected] -8 points 1 month ago* (last edited 1 month ago) (2 children)

You did the right thing. OOP was invented by people who were worried about their job security, to obstruct others from understanding their code.

[–] Lightor 18 points 1 month ago (2 children)

OOP is pretty readable though. What would be the alternative, functional programming with no ORM?

[–] [email protected] 6 points 1 month ago

Right, most things are a fine thing in moderation.

[–] [email protected] 3 points 1 month ago* (last edited 1 month ago)

Well, bad code is bad code regardless of the paradigm. I've just had bad experiences rewriting some horrible OOP codebases and opted out to use as much functional style as C# allowed me to.

The main problem, as I see it, is that OOP encourages unnecessary abstractions and inheritance. These should be used as little as possible, because they typically increase complexity and make code harder to read and untangle. As an example, I've seen people define interfaces that don't essentially define anything.

Another problem is that OOP encourages mutable member variables. It's very annoying to try to understand code where class C inherits from class B that inherits from class C. Good luck debugging when the methods of C modify a variable declared in A in subtle ways.

As an idea OOP is very appealing. When I was younger, I would be thrilled to start designing a class hierarchy and interfaces when encountering a new programming challenge. Now I just try to think how to make things as simple and modular as possible.

Edit: of course bad functional code is also bad code. It's also very annoying to try to understand code where functions pass badly named functions around as parameters and use 10 function compositions in a sequence.

[–] LavenderDay3544 8 points 1 month ago (1 children)

Obfuscation Oriented Programming as I call it

[–] marzhall 2 points 1 month ago

Damn I'm stealing that

[+] [email protected] -8 points 1 month ago (1 children)

Good, OOP can suck my balls

[–] [email protected] 11 points 1 month ago (2 children)

Balls.suck() is the correct syntax.

[–] [email protected] 4 points 1 month ago (2 children)

Don't you need to declare new Balls() first? Or do you suck() Balls static?

[–] [email protected] 7 points 1 month ago* (last edited 1 month ago) (1 children)

BallsFactory ballsFactory = new BallsFactory();
ballsFactory.setSuckable(true);
Balls balls = ballsFactory.create();

[–] whats_all_this_then 10 points 1 month ago* (last edited 1 month ago) (1 children)

All of this is okay, but it's not production ready. This is what real production code looks like:

SuckableFactory suckableFactory = new SuckableFactory();
Suckable balls = suckableFactory
    .setShape(SuckableShapes.round)
    .setCount(2)
    .create();

SuctionProvider mouth = SuctionProvider.getInstance();

SuckerFactory suckerFactory = new SuckerFactory();
Sucker sucker = SuckerFactory.create():

sucker.setSuctionProvider(mouth);
sucker.setSuckable(balls);
sucker.setIntensity(SuckerSuctionIntensities.medium);
sucker.suckSuckable();

[–] whats_all_this_then 13 points 1 month ago

Python port:

from ballsucker import suck
suck()

[–] [email protected] 3 points 1 month ago

Or I didn't using the correct naming convention!

[–] [email protected] 2 points 1 month ago

Actually, it would be OOP.suck(ddplf.getBalls())