There are few fields in this world, as far as I know, where the speed of a PhD can be extremely dependent upon how you spent your time as a 10-year-old.
I was thinking recently about why I have been pretty slow in getting my PhD. One of the reasons is that I did not grow up a hacker. This means that when I have an idea that I need to implement in order to test and experiment, the success of my experiment rests very highly on my ability to implement it quickly, effectively, and successfully, and I had to learn all those skills all on my own. In the biological sciences, bench skills are usually taught either in lab classes, or at the very least in the lab when you get trained by a prof or a postdoc. But few people enter the biomedical sciences having had a decade of experience with bench work and the various techniques PRIOR to entering even college, let alone graduate school.
In my world, no one uses the word "train" describe what they do to nascent graduate students; they either know shit about computers or they don't. If they don't, they usually drop out because it's so hard to compete - you might have good ideas but if you can't implement them, you lose. End of story. This may be a reason why there are so few girls in the area, I don't know many girls who hacked all their lives, even fellow computer scientist chicks. In graduate school for computer science, all focus is on idea generation and testing of said ideas, and very little about training.
Because of this, I will totally and unabashedly say that if there were no Google, I could not get a PhD in computer science. Hands down, absolutely, totally true. There are too many things out there that I just don't know about that I had to use Google to figure out. Some are basic and some are complex. I think I will thank Google in my thesis acknowledgments.
1) Compiler error X when building software Y.
Thanks to google and experience, I now understand and recognize most errors. However, sometimes I don't know how to fix them, but the plethora of mailing lists usually helps me figure out fixes or patches. I don't know how many blogs, mailing list archives, and whatnot I've trolled to figure out various things that have NOTHING to do with the idea I am trying, but everything to do with figuring out how to properly set up an environment to test the idea I am trying.
2) Finding helpful tools.
Without google, I would not have found various software tools that help me with my work. Writing your own tools is a bitch sometimes, and in the end, it's just great when someone else has written it already. But I wouldn't know about it without Google.
3) Little definitions.
Sometimes I just can't remember this little technical definition or that. Instead of having to go to the library, find the section that I think covers what I want to know, flipping through the index only to find that I'm wrong, and moving on to the next book until I find what I want to know, I can just ask google. For example, recently I needed to know what a Gini coefficient meant with respect to forming a decision tree. I had no idea - but Google did. Thanks Google!
In short, I think Google has revolutionized my ability to do what I want to do. It has (sort of) leveled the playing field such that it wasn't such a bitch to catch up to my fellow graduate students who have been living the dork-lifestyle since they were small children. It frustrated me to no end in the beginning of grad school about how I just didn't know stuff that I needed to know to get shit done. Not only did I have to learn about the field in order to properly think of new research directions, but I had to learn a crapton of other shit in order to be an effective researcher. It was a tremendous barrier to entry. Tremendous.
How can this be changed???? I don't know. I'll have to think about it.
2 years ago