|
|
|
|
|
by chomp
1029 days ago
|
|
You're reading it right at face value, however I concede it's possible this student has long since graduated. I somewhat routinely go out with my former CS professors (I've known them for almost 20 years at this point). They currently express some of the frustrations that this student has, but on the teaching side. As I was told, the US is relatively split 50/50 between programs that teach the computability theory first and foremost, and programs that teach practical development. The problem as I was told, is that the computability theory method is a drag on student achievement. Many want to revamp their departments to ease students into things like automata, complexity, and architecture concepts, but there is a lot of push back from existing professors. Students are entering the program these days without being able to grok even simple boolean statements (true && !false). OpenAI is removing a lot of opportunities for these students to self-learn. Most departments understand that they need to revamp. However, you have faculty who each are experts in their own slices of CS, and most are hesitant to change: "The real problem is that kids these days need more data science" "No the real problem is kids these days need more distributed computing". The result is that it's difficult for departments to come to an agreement on a proper on-ramp, so they cling to existing programs. It's known that the incoming generation is less tech savvy than the prior. The question is if CS faculty can restructure their departments to sync with the new generation, and the field as it exists today. |
|