I won't deign to respond to anything else you say, but you should understand how encompassing software engineering is and that it clearly at some point has to evolve to account for modern needs.
What? This comment makes no sense. Also, it isn't condescension. I'm educating you. You probably thought your professors and your dean were condescending to you. Right? Everyone who knows more than you, I suspect most people, are condescending to you? Got a chip on your shoulder?
> I won't deign to respond to anything else you say
Who cares? Then don't.
> but you should understand how encompassing software engineering is
Does it sound like I don't. I know what CS is and I know what software engineering is. I know enough not to use those terms interchangeably.
All you've shown is that you don't what what computer science is and you don't know what software engineering is. Instead of playing the victim, have some humility and take this opportunity to learn. Something you should have done when you were in college.
Also, you sound like a "jobless english/journalism major who turned to being a 'software developer' for a job". I can't think of any self respecting "hacker" or a developer who can't learn web development ( at least to a moderate level ) on their own. It's an easy tell to actual developers and hackers.
Software engineering is a different discipline from computer science. It deserves its own major, and does not deserve to be mocked as a "jobs program".
What's the difference? Computer science is about the theory of computation, and the analysis of algorithms, and to some degree about the design of computer languages. Software engineering is about the efficient construction of larger-scale programs that adequately meet the need.
(Yeah, "efficient" is a lie. "Somewhat less inefficient" is closer to the truth. And "construction" should really be "construction and maintenance".)
The fundamental problems in software engineering are really about the brain-to-brain transfer of technical information between teams (and generations) of engineers working on large code bases. Those are not problems that are within the scope of a computer science degree.
It's called computer science, not web development for a reason.
> I ask sincerely just because when I pushed for change in curriculum, I basically was shown the door that led to me dropping out and (thankfully) landing a gig at a startup that opened up another (better) door for me.
Okay. Good for you. But what's your point? Are you saying that universities should be a "jobs program" rather than an institution for higher learning?
> I ask sincerely just because when I pushed for change in curriculum
"I am not a CS degree holder. But I did attempt a masters in software engineering". So you don't know what computer science is and yet you feel qualified enough to recommend a curriculum change?
Are you going to denounce your mechanics professor for not incorporating "changing tires" into his curriculum? It's unbelievable that your comment is the top voted comment here. The quality of comments on "hacker" news...