I don't know how CS is taught these days. In the 1980s I learned a lot about data structures, algorithms, and programming languages, virtually none of which I ever directly used in my later career. I've never had a job that required leetcode knowledge. I've never had to write a sort or a search or a tree balancing algorithm from scratch. There are libraries for anything you might want to do (and if there aren't, that's often a big red flag that you're doing something wrong).
I learned almost nothing about engineering. It took me quite a while on the job to learn and appreciate the practices that result in long-lived, maintainable systems. Overly complex, fragile systems with inscrutable interdependencies using esoteric frameworks are often the product of smart people who don't understand engineering principles (yet we often call them "engineers").
I learned almost nothing about engineering. It took me quite a while on the job to learn and appreciate the practices that result in long-lived, maintainable systems. Overly complex, fragile systems with inscrutable interdependencies using esoteric frameworks are often the product of smart people who don't understand engineering principles (yet we often call them "engineers").