3 ms·

>> seems the downvoters don’t like what I have to say, but that doesn’t make it less true. Except that it isn't true. A quick look at https://cs.stanford.edu/d

>> seems the downvoters don’t like what I have to say, but that doesn’t make it less true. Except that it isn't true. A quick look at https://cs.stanford.edu/degrees/ug/Requirements.shtml https://cs.stanford.edu/degrees/ug/Requirements.shtml paints a completely diffrent picture.

aliston 7y ago
Please point out where something I said isn’t accurate.
- likhuva 7y ago
  >> no compilers or os, no multivariable calculus, no pointers. Stanford still requires cs students to take classes that cover the material above (except compilers which can be taken as a specialization)
  - aliston 7y ago
    That’s just not true - they all became depth electives or not required at all. OS is 140. Not required. Multi var calculus is math 51. Not required. As you note, compilers is not required. They also removed the EE hardware class in favor of a mishmash of core cs classes that are easier.
    - jdashg 7y ago
      It depends on the track. HCI for instance doesn't require those, but other tracks do. CS isn't just about printing software engineers.
manfredo 7y ago
Stanford did indeed make some changes that I feel did significantly impact the rigor of the courses. Most notably, CS106 (A, B and X) and 107 all introduced team assignments, but the assignments themselves largely did not change. So you have twice the workforce for each assignment. I feel like this also meant that when a pair consisted of two people of different levels of skill the quicker student finds and fixes most bugs, thereby depriving the weaker student from developing debugging skills. Without pair programming the latter would eventually develop those skills but it would take longer and require more assistance from section leaders. I think it's a bit crude to say it's been "dumbed down" but it is not entirely untrue. Also I don't think this has anything to do with "SJWs", these changes were directly prompted by staffing shortages.

aliston 7y ago

Please point out where something I said isn’t accurate.

likhuva 7y ago
>> no compilers or os, no multivariable calculus, no pointers. Stanford still requires cs students to take classes that cover the material above (except compilers which can be taken as a specialization)
- aliston 7y ago
  That’s just not true - they all became depth electives or not required at all. OS is 140. Not required. Multi var calculus is math 51. Not required. As you note, compilers is not required. They also removed the EE hardware class in favor of a mishmash of core cs classes that are easier.
  - jdashg 7y ago
    It depends on the track. HCI for instance doesn't require those, but other tracks do. CS isn't just about printing software engineers.

manfredo 7y ago

Stanford did indeed make some changes that I feel did significantly impact the rigor of the courses. Most notably, CS106 (A, B and X) and 107 all introduced team assignments, but the assignments themselves largely did not change. So you have twice the workforce for each assignment. I feel like this also meant that when a pair consisted of two people of different levels of skill the quicker student finds and fixes most bugs, thereby depriving the weaker student from developing debugging skills. Without pair programming the latter would eventually develop those skills but it would take longer and require more assistance from section leaders. I think it's a bit crude to say it's been "dumbed down" but it is not entirely untrue. Also I don't think this has anything to do with "SJWs", these changes were directly prompted by staffing shortages.