393
you are viewing a single comment's thread
view the rest of the comments
[-] Miaou@jlai.lu 8 points 5 months ago

I have the same problem with oop. 10 levels of encapsulated calls just to see you were in an overridden methods without enough data to find out which implementation it was. Ugh

[-] azertyfun@sh.itjust.works 1 points 5 months ago

I mean, bad programming sucks regardless of the "paradigm" (and vice-versa, mostly). But as someone whose job it often is to sift through production logs hunting for an issue in someone else's component, at least I have a chance with OOP, because its behavior is normally predictable at compile time. So with the source and the backtrace I can pretty reasonably map the code path, even if the spaghetti is 300 calls deep.

Now where shit really hits the fan is OOP with dependency injection. Now I'm back to square 1 grepping through 15 libraries because my LSP has no idea where the member comes from. Ugh.

this post was submitted on 30 May 2024
393 points (94.6% liked)

Programmer Humor

32461 readers
590 users here now

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

Rules:

founded 5 years ago
MODERATORS