4 ms·
And that would be the difference between a CS curriculum and a Software Engineering course that someone might attend anywhere other than a Top 100 university. T
by rbrtl 6y ago
And that would be the difference between a CS curriculum and a Software Engineering course that someone might attend anywhere other than a Top 100 university. They are discrete curricula and the criteria to get on to SE tend to set a lower bar.
- justin66 6y agoThat's pretty interesting. I wonder if sitting for the PE exam were a legal requirement for calling oneself a "software engineer" in the United States, they'd raise the bar for admittance to those programs. (and honestly, improve the SE curriculum somewhat) As it stands, the trend towards licensing software engineers seems to have reversed itself recently. [1] https://www.nspe.org/resources/pe-magazine/may-2018/ncees-ends-software-engineering-pe-exam https://www.nspe.org/resources/pe-magazine/may-2018/ncees-en...
- rbrtl 6y agoI was discussing this with my dad earlier today. Neither he nor I have a degree. He started a course in the 70s that he never finished, and I didn’t apply to university, for numerous reasons, but I was application age when fees were tripled to £9k, and the loan repayment structuring made it apparent that 80% of these degrees weren’t worth the money. My current role title is Software Engineer, but I don’t go by it outside work very often because Engineer means something outside the technobubble. I have a friend with two degrees in aeronautical engineering, and he clenches every time he hears someone refer to me as an engineer. I agree with him too, but earning that title should be about more than a degree, engineers in industry almost always have to work under a supervising engineer for a significant period of time before acceding to the title themselves.