> I’ve seen more and more people dismiss the idea of universities, and more generally, dismissing the idea of learning anything that isn’t explicitly needed for

> I’ve seen more and more people dismiss the idea of universities, and more generally, dismissing the idea of learning anything that isn’t explicitly needed for the career they’re studying for. This always felt like a huge mistake to me. As usual, it's not black and white: there's no single answer that fits everyone or every field. That said, I'll give an example from computer science where I've seen many people struggle if they haven’t taken (and approved) a course on operating systems: topics like race conditions, mutexes, and concurrency. While these aren't especially difficult concepts, they're not inherently tied to knowing a specific programming language. They transcend language syntax, even though some languages offer syntax for handling them. The problem I often see is twofold: either developers don't apply locking mechanisms at all (leading to unsafe behavior), or they use them excessively or incorrectly, resulting in deadlocks or significant performance issues. Clearly concurrency could be really hard but I am talking here about the basics.