This is an evolving list of Web resources for career in research. There is a wealth of information on the Web. If you think any of this should be added to the list, or if you'd recommend removing some items from the list, send me mail at ramesh@usc.edu.
How to Succeed in Graduate School: Marie DesJardin's monograph discusses the various stages of a graduate student's career. It also has some advice for advisors!
Networking on the Network: Good advice on how to join the community, and build contacts.
How to do Research at the MIT AI Lab is another collection of advice on research methodology and skills.
Dave Patterson's ``How to Have a Bad Research Career'': While this is mostly advice for junior faculty, it does frame the way you should be thinking about your research.
Academic Careers for Experimental Computer Scientists and Engineers is a resource for when you've decided on a career in academia and want to understand what challenges await you.
The CRA's Workshop on Academic Careers is another similar resource.
You and Your Research contains Richard Hamming's observations on research. (Thanks to Eric Coe for this link).
Elements of Style, Strunk and White's classic book on writing, a MUST read for any Ph.D. student. In fact, I'd recommend re-reading this book every year.
Mathematical Writing is a neat collection of do's and don'ts for technical writing, with special emphasis on mathematical writing.
Ed Tufte's Visual Display of Quantitative Information has a wonderful discussion of the principles of graphical presentation of data, a must for every systems Ph.D. student.
Writing Systems and Networking Article is a comprehensive writing guide with pointers to other literature on the subject.
Presentation Skills is a list of pointers to resources for effective oral communication.
Ed Tufte's Advice on Presentations. Make this second nature!
Efficient Reading of Papers in Science and Technology: A very succinct description of a methodology for reading scientific papers. Re-read this frequently until you've mastered the methodology.
Sugih Jamin's checklist for paper reading contains questions you should be asking while reading a systems paper.
The Task of the Referee, Alan J. Smith's classic monograph on the responsibilities of a computer science reviewer. This paper also has some pointers to other literature on the subject.
A Guide for New Referees in Theoretical Computer Science: Ian Parberry's guide is useful as a general guide for reviewers, despite its title.
The GNU Coding Standards. A description of the GNU standard coding style for C. Highly recommended. There are other C coding styles (such as K&R), so you should feel free to pick the one you like.
The Perl Style Manual: Coding styles for Perl scripts.
The Ellemtel C++ Style Manual. A coding standard for C++. There are many such. Feel free to use any you like.