3 ms·
While the (original HN) title may have been a bit on the pretentious side, the linked syllabus explains the rationale for the course: > This course examines pa
by Jtsummers 6y ago
While the (original HN) title may have been a bit on the pretentious side, the linked syllabus explains the rationale for the course:
> This course examines papers every computer scientist should have read, from the 1930s to the present. It is meant to be a synthesizing experience for advanced students in computer science: a way for them to see the field as a whole, not through a survey, but by reliving the experience of its creation. The idea is to create a unified view of the field of computer science, for students who already know something about it, by replaying its entire evolution at an accelerated frame rate.
Which is not a bad idea. Many computer scientists, programmers, and software engineers have an ahistorical understanding of CS. See the discussion the other day when someone claimed "software engineering" is only 20-30 years old. They aren't a one-off, though probably not the majority. A significant number of people in this field don't know the history of it: how it was developed, what dead ends were hit, what dead ends turned out not to be dead ends (often once we got fast enough hardware), etc.
Similar to the ethics course in many engineering/science curricula, it's something that seems a bit superfluous but turns out to add a great deal of value if students can be bothered to explore it.