I think a lot of 2025 developers would be alarmed to think that a project had started from an object-oriented design perspective.
I think a lot of 2025 developers would be alarmed to think that a project had started from an object-oriented design perspective.
Then you have data (growing above average), scripting and partially frontend that are done differently, but they are still a minority of the job market.
(I'm not a Lisp or functional partisan; like I said downthread, it's Go and Rust for me these days mostly).
Keep my original point in mind here, which is simply that OOP principles are not a fundament of software development in the same way algorithms, data structures, memory models, and concurrency are. We're discussing curricula that have students learning class-based object-oriented programming as expressed in Java as a requirement, and basic systems programming as an elective. That's backwards.
I don't care if you still use OOP. I'm not advocating for its removal from production codebases. There are plenty of things that earn their keep in modern product stacks that aren't fundamentals of computer science!
And when you look at what the actual classes teach: it's usually patterns-y Java. GoF patterns are effectively obsolete. You might still need to grok them, but that's trade knowledge, not fundamental computer science. You don't come out of a CS degree knowing Hibernate or SAP, either, but people figure it out on the job.