Computer science programs shouldn't act like they are teaching future software engineers, because they shouldn't be. Global curricula recommendations for various computing fields, including computer science, software engineering, information technology, and more, are published by the ACM, IEEE Computer Society, and other global computing organizations (https://www.acm.org/education/curricula-recommendations), and ABET has accreditation guidelines for computing programs (computer science, information technology, cybersecurity, and information systems) and engineering programs (including software engineering, computer engineering, cybersecurity engineering). There's no need to "turn computer science degrees into some vocational pseudo-bootcamp that just teaches the hot framework de jour" because specific recommendations and guidelines are designed to set students up for long-term success in their chosen field.
Cybersecurity has already made its way into both computer science and software engineering programs, assuming universities are keeping up with curriculum recommendations, accreditation guidelines, and (where appropriate) engaging with industrial advisory boards. The guidelines also cover societal impacts and professional ethics, although I have issues with ethics being embedded in courses rather than taught in a dedicated course - I had to take a dedicated engineering economy course, but ethics was tacked on as modules on other courses and most ethics courses were general.
I'm rather surprised that the author didn't have a performance class. Analysis of algorithms is a key computer science course, even for someone studying software engineering. And software engineering should cover performance from a requirements, architecture, design, and verification perspective. It sounds like the author's program is missing some important required content.
I'm struggling to understand the author's point.
Computer science programs shouldn't act like they are teaching future software engineers, because they shouldn't be. Global curricula recommendations for various computing fields, including computer science, software engineering, information technology, and more, are published by the ACM, IEEE Computer Society, and other global computing organizations (https://www.acm.org/education/curricula-recommendations), and ABET has accreditation guidelines for computing programs (computer science, information technology, cybersecurity, and information systems) and engineering programs (including software engineering, computer engineering, cybersecurity engineering). There's no need to "turn computer science degrees into some vocational pseudo-bootcamp that just teaches the hot framework de jour" because specific recommendations and guidelines are designed to set students up for long-term success in their chosen field.
Cybersecurity has already made its way into both computer science and software engineering programs, assuming universities are keeping up with curriculum recommendations, accreditation guidelines, and (where appropriate) engaging with industrial advisory boards. The guidelines also cover societal impacts and professional ethics, although I have issues with ethics being embedded in courses rather than taught in a dedicated course - I had to take a dedicated engineering economy course, but ethics was tacked on as modules on other courses and most ethics courses were general.
I'm rather surprised that the author didn't have a performance class. Analysis of algorithms is a key computer science course, even for someone studying software engineering. And software engineering should cover performance from a requirements, architecture, design, and verification perspective. It sounds like the author's program is missing some important required content.
[dead]
[dead]