Hacker News new | past | comments | ask | show | jobs | submit login

The key part of curriculum design is prioritization because you generally have a fixed amount of hours for a degree - every important thing you put in requires taking out something else, and learning a topic in more detail requires learning fewer topics. And I'm not sure if most potential students would value spending a year on bare metal at the cost of throwing out a year's worth of stuff that is more high level. Like, be specific - count the things you're adding, take a look at the CS/SE courses in the program you had, and choose an equivalent number of courses that you would cut out to make space for your proposals - does it still make sense then?



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: