flâneur — a map of the web's best reading

How to Find Research Problems

cs.jhu.edu · 1,344 words · saved by 1 readers

Written by Jason Eisner in 1997, for new Computer Science Ph.D. students at the University of Pennsylvania. He was a grad student himself at the time. Here's a Chinese translation. Computer science includes many different kinds of research efforts, some of which are more tyrannosaurical than others. You can contribute to one of these efforts in various ways. While this doesn't get you points for originality, it may be useful, both to your education and to the field. If you can make it useful to enough people (say, by making it portable and Web-available), it might even get your name known. [Update: It may also be a good starting point. King (2006) describes "how to write a publishable paper by beginning with the replication of a published article." More here and here.] When reading papers, stay on the lookout for such bones. In particular, notice when the author may be making harmful simplifications or arbitrary choices in his/her approach. These are opportunities for you to try someth

How to Find Research Problems Written by Jason Eisner in 1997, for new Computer Science Ph.D. students at the University of Pennsylvania. He was a grad student himself at the time. Here's a Chinese translation . How to Find Research Problems by Jason Eisner The biological anthropologist Loren Eiseley used to say there were two kinds of scientists: big-bone hunters and small-bone hunters. (He himself was a small-bone hunter, he said, fitting little bits of data into the skeleton. If Eiseley had been a programmer, he would have called this "bottom-up science.") Computer science includes many dif

Explore this link on the map →

saved by

related reading