3 ms·

I think you're forgetting how computer science programs operate. You're listing a bunch of specialty skills that are likely covered once in a topic class and ne

I think you're forgetting how computer science programs operate. You're listing a bunch of specialty skills that are likely covered once in a topic class and never again. You said "I don't mean data structures and algorithms," which excludes the actual foundational skill that they had to build on in every class, in addition to raw programming chops. Why don't they know database systems? They might have taken a database course for 4 months 3 years ago and never touched a database again because it's not a trade school. School just validates that you can learn a series of related skills over a few months when necessary. What's the last thing you started and dropped after a few months just before the pandemic? How comfortable would you be if you interviewed for a job exclusively on that skill?

gardenhedge 4y ago
This. I have 10 years experience. I might have done a successful project in Ruby in year 2 and maintained it for years 3,4,5 but haven't touched it since then.
sime2009 4y ago
The original complaint is that student aren't even getting the 4 month introduction to topics like databases and concurrency. Later on in their career they wander into them and don't even realise there exists large body of important theory and knowledge for things like databases and data modelling. They get then get into trouble and assume "Well, I guess programming is just hard". Similar story for concurrency. These people later on naively create systems which are full of concurrency problems and are then puzzled as to why sometimes it breaks for no clear reason.