this post was submitted on 14 Apr 2026
20 points (100.0% liked)
Programming
26510 readers
93 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You need to have a general idea what structures and algorithms those libraries are using, so you know if they're a right fit for your use case,what configuration options to use, and how they'll scale. Design patterns are good to learn (required even), but I wouldn't go too deep into them. IIRC, that Design Patterns book goes a little too crazy and gets a little too abstract in some cases, and is what caused all that Enterprise Java craziness. The profession seems to be currently moving away from that kind of OOP, and moving to OOP-ish + some functional programming concepts mixed in (Rust, React, etc).