Re:Syllabus for Classics of Computer Science
by bawolff on Tuesday January 19, 2021 @11:32PM
(#25842606)
> Books every English professor should have read
That's a weird example. There is an actual western canon and you're probably a bad english professor if you aren't familar with it.
Re:Syllabus for Classics of Computer Science
by newbie2020 on Wednesday January 20, 2021 @02:15AM
(#25843453)
We are taught the important bits of a lot of this in the regular coursework since it is fundamental to the field. I think these lists are for the people who might enjoy walking through the development of the field for their own pleasure and curiosity. And to learn something in the process!
Re:Syllabus for Classics of Computer Science
by dinvlad on Tuesday January 19, 2021 @11:47PM
(#25842677)
Better still, "The List of StackOverflow questions every developer should know, but looks up every damn time"
Re:Syllabus for Classics of Computer Science
by tomerbd on Wednesday January 20, 2021 @12:10AM
(#25842784)
Is there such a list?
Re:Syllabus for Classics of Computer Science
by Larrikin on Wednesday January 20, 2021 @01:06AM
(#25843052)
How to exit vim is almost certainly number one
Re:Syllabus for Classics of Computer Science
by buzzerbetrayed on Wednesday January 20, 2021 @01:29AM
(#25843166)
Just restart your computer. That ought to do it.
I've seen shit like this in every field...
"Books every historian should have read."
"Books every English professor should have read."
"Books every psychoneuroendocrinologist should have read."
They're all a collection of shit that someone, somewhere - usually with an inflated self of self - feels qualified to tell you and every other person that they should have read.
You know what you should have read? Papers you find interesting that advance your understanding for the problems you face. Understand I'm not saying that every list everywhere is a load of horseshit that you need to ignore - I'm not. I'm saying be wary of all-encompassing "lists" of "things" you "should" do / know / read / experience.
EDIT: LOL, stealth edit on the title... from "Papers every computer scientist should read" to "Syllabus for Classics of Computer Science".
Well... at least the pretension took a backseat. :)