Discussion about this post

User's avatar
Alexander Ptakhin's avatar

I would say maybe we can leave the CS degree to universities for people who want to do science. Hence, the Software Engineering discipline might not be suited to universities, but rather to specialized technical schools and colleges, as it’s a more engineering-oriented profession.

Wayne Sadin's avatar

In 1970, I started my BS in CS degree at a state university. The chair of the department made something clear during the first class meeting: "this is not a technical school. We're not going to teach you how to use our computer center (S/360 67 running VM + MFT guests), nor how to write a program that compiles & runs, nor how PL/1 compares to COBOL. You'll learn those things as you go, to get your assignments done.

We're going to teach you the underlying principles that allow you to understand any operating system, compiler, language, problem type & programming solution.

What you learn here & now will serve you forever. "

56 years later I'm a CIO (been one since 1982), and I still remember 'Goto statement considered harmful,' & Denning's 'locality of reference,' & why latency trumps bandwidth for conversational workloads, & some of 'Formal Languages & Their Relationship to Automata,' & why RSA works (until Quantum, anyway)...

I don't require (or even prefer) a CS degree for developers, because most coders can solve most business problems using straightforward techniques & the tools (+ JIT training) provided by employers.

But when I hear hype about a new technology, or review a glib 'technical' justification, or I'm getting briefed on an intricate problem, the principles I struggled to master 50 years ago still serve me.

2 more comments...

No posts

Ready for more?