this post was submitted on 19 Jul 2025
25 points (87.9% liked)

Programming

24072 readers
342 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
25
The Big OOPs: Anatomy of a Thirty-five-year Mistake [Casey Muratori] (www.youtube.com)
submitted 5 months ago by cm0002@lemmy.world to c/programming@programming.dev
4 comments fedilink hide all child comments
 

“Compile-time hierarchy of encapsulation that matches the domain model was a mistake.”

https://en.wikipedia.org/wiki/Casey_Muratori

you are viewing a single comment's thread
view the rest of the comments
[–] NigelFrobisher@aussie.zone 9 points 5 months ago

So much time in my undergrad designing stupid inheritance hierarchies for systems (petrol stations, web servers, guidance systems), none of it even remotely applicable in my actual career as a dev. In fact, practically every time someone had done something “clever” with inheritance it caused subtle bugs or made maintenance and extension much harder than it should have been.