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).
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments