|Undergrad seeking Compiler Construction Grad Studies shyatt@sol.UVic.CA (1994-02-22)|
|Undergrad seeking Compiler Construction Grad Studies email@example.com (1994-02-23)|
|Re: Undergrad seeking Compiler Construction Grad Studies firstname.lastname@example.org (1994-02-23)|
|Re: Undergrad seeking Compiler Construction Grad Studies email@example.com (1994-02-26)|
|From:||firstname.lastname@example.org (Darin Johnson)|
|Organization:||University of California, San Diego|
|Date:||Sat, 26 Feb 1994 18:29:37 GMT|
> read ACM Transaction of Programming Languages and the ACM PLDI
> Compiler Construction conference. See who is doing the stuff that
> interests you... Then, try to contact that advisor directly and tell
> them why you think their work is the best approach.
Except - the people you discover this way tend to be swamped with students
and can't take anymore. It's still good to look at the school itself
instead of just the advisor, since there is a good chance that you will
change your area, and evem a slight change in topic can scare off an
advisor. And a school with a large number of profs in compilers will give
you more opportunity to wisely choose an advisor when you need to (not in
the first year).
Also, good advisors do not necessarily correspond to good researchers.
Thus you could end up doing grunt work for a famous person for 5 years,
with only minimal input for your own research. Younger, less famous
advisors tend to have more time to work with you and more enthusiasm.
Return to the
Search the comp.compilers archives again.