[slg]

It seems like many if not most computer science students are actually interested in software engineering and not CS. It is a shame that more schools don't offer separate software engineering programs or at least make the distinction between the two more apparent to prospective students.

I am sure I wasn't the only 17 year old told I should get a CS degree if I wanted to be a software developer. Meanwhile the most value I have gotten out of the CS classes that taught me to write a loop in MIPS or two build a XOR gate out of NAND gates is commiserating about those experiences with fellow CS grads. I would have much rather had a class about reverse engineering an API or other less theoretical and more vocational classes.

[chii]

Knowing how a loop is implemented in MIPS means your now have enough knowledge to debug assembly, and perhaps do low level performance optimisations. It's not useless, just not directly and immediately. You won't be able to lean on any foundational work if you hadn't learnt it, and you'll have a super hard time doing complex things later, like reverse engineering.

[slg]

What percentage of developers ever have to debug assembly or do low level performance optimizations? I am 10 years into my career and I have only professionally seen assembly code once. We have abstracted most of these low level things out of the normal life of most developers. That isn't to say it isn't important for some, but there are a lot more developers who would benefit more from a class on design principles than a class on assembly.