Learning computer architecture is fine and good and useful, but in a secondary fashion to help understand the main tool people in CS use. However, it is not the core of what makes computer science "computer science", or even the main thing that makes CS grads hire-able, despite the common misconception that computer science is about computers.
I would emphasize something along the lines of an HtDP approach developed by Felleisen et al. which goes beyond just the coursework in the HtDP book [0]. It extends into several core courses and in fact much of the core CS curriculum was being overhauled by Felleisen until Northeastern unceremoniously decided to dumb down the curriculum to satisfy some idiotic administrative idea of "market fit" and the desire to homogenize content across their expanding network of satellite campuses. When the curriculum was implemented, companies became very hungry for NU CS graduates, esp. given their experience with them during co-ops.
CS curricula are sadly being bootcampified, because that is the will of university administration.
I would emphasize something along the lines of an HtDP approach developed by Felleisen et al. which goes beyond just the coursework in the HtDP book [0]. It extends into several core courses and in fact much of the core CS curriculum was being overhauled by Felleisen until Northeastern unceremoniously decided to dumb down the curriculum to satisfy some idiotic administrative idea of "market fit" and the desire to homogenize content across their expanding network of satellite campuses. When the curriculum was implemented, companies became very hungry for NU CS graduates, esp. given their experience with them during co-ops.
CS curricula are sadly being bootcampified, because that is the will of university administration.
[0] https://htdp.org/