|
 |
Invisible wrote:
> I very much doubt you can actually do a PhD in "doing cool stuff with a
> computer". It's a tad vague, eh?
The way it works (here at least) is that there is someone who is sponsoring
and tutoring you called your "adviser". He has a particular area of interest
(like compiler construction, network protocols, or whatever), and he helps
you pick a topic that would be interesting, publishable, etc.
So what you need to do if you want a PhD in something you find interesting
is go to universities and find out what potential advisers are interested
in. You won't be able to do a PhD on Haskell compiler optimizations if
nobody at the university is interested in compilers.
> My course was 4 years too, but it was only a BSc. I might be wrong about
> the MSc requirement, but that's what I heard.
I said that's true of the places I looked in the US, and someone
contradicted me and said the UK works differently.
> Besides, don't you have to, like, spend years searching through the
> library to find every piece of work that has ever been written about
> your subject,
No. That's why you have an adviser. He tells you where to look for related
information. There's a lot of reading and understanding, and you need to
summarize it enough to show why what you're doing is different, but that's
about it.
> ancient sage to consult on the works on the Ancient Masters to see if
> they have anything relevant to add?
That's why they invented university libraries. :-)
> I don't think I could do that from my desk at work.
I was often met with astounded surprised when I mentioned that I was paying
my own tuition. You don't need a job to get a PhD if you get accepted.
> Meh. I doubt it. It seems everybody just asks "how many years' coding
> experience do you have?" and "what are your customer service skills like?"
You'd be applying for different jobs.
--
Darren New, San Diego CA, USA (PST)
"Ouch ouch ouch!"
"What's wrong? Noodles too hot?"
"No, I have Chopstick Tunnel Syndrome."
Post a reply to this message
|
|
