4 ms·
It's good, but quite often, I've faced the problem of an information overload, where there are just too many things to read. How have you all tackled it?
by xtacy 17y ago
It's good, but quite often, I've faced the problem of an information overload, where there are just too many things to read. How have you all tackled it?
- mahmud 17y agoThat's why I found it more fruitful to study entire compilers/projects, instead of hunting down papers on memory management, code generation, optimization, evaluation models, etc. If you get into the "mind" of the project, you will be able to trace the progression of ideas and see why things were done the way they were. I often read peripheral papers on a given project because I tend to get the big picture from those filler papers, usually written by the lead, and/or coauthored with the entire team. The highly technical papers reserved for the best and most specialized conferences usually skim the details and present the most novel idea in its purest crystal form .. usually under length restrictions and addressing a well prepared audience. I recommend a beginner to memory management start with Wilson's Uniprocessor Garbage Collection Techniques ftp://ftp.cs.utexas.edu/pub/garbage/bigsurv.ps Abstract: http://www.memorymanagement.org/bib/wil94.html http://www.memorymanagement.org/bib/wil94.html
- xtacy 17y agoThanks. Yes, that's why teachers will never be not-wanted. We need experts/teachers who can cherry pick concepts and help us sift through the maze. Thanks for the link!
- epochwolf 17y agoMy first choice is to find an expert and pick their brain to find the stuff I need to read. I hang out in various irc chatrooms. There are usually one or two experts I can bug for references. Alternatively, a good way to find authoritative works in a list like this is to read the references at the back of each book. If most of them refer to the same three or four books you'll want to read those first. You can try looking up the books on wikipedia and seeing what is sad about them.