IU Engineering PhD
Experiencing something N=1 times qualifies me to give advice, right? Maybe not, but here are some IU-specific tips anyway.
What are the official milestones?
In graduate school, there are official milestones (forms to be signed) and unofficial milestones (your committee thinks you're ready). Indiana University engineering is no different in this regard. Early on, because the engineering department was new, some of these forms were difficult to find. But over time this dramatically improved. Some of these cross-link to each other, but I still found it useful to bookmark them all for quick reference. These are the links I shared most frequently with fellow graduate students here at IU:
- DO attend the public portion of defenses given by your peers. You can get a feel for what yours will be like by observing others by the same faculty or at least within your school.
- DON'T watch defense dissertations on YouTube. Or if you do, be cautious about it. If someone shares it on YouTube, it's probably an outstanding presentation by a rock star candidate, rather than a typical presentation by average candidate. And frankly, most of us are average candidates, so comparing yourself to what's shared on social media is a recipe for imposter syndrome.
- DO practice public speaking as much as possible beforehand. I want to clarify that practicing public speaking is about increasing your comfort and confidence. This is separate from increasing your skill. For that, you need feedback. You can record yourself and then review it later on your own, or you can get feedback from your audience. Personally, I get the best feedback from audience members who are not intimately familiar with my work.
- Pay attention to the official milestones (see above).
- Ask your advisor about the unofficial milestones. The unofficial milestones are part of the culture of your committee, your department, and your school. It might be possible to satisfy all the official milestones but miss something important which might endanger your success. One mistake I made in my research proposal was a much too ambitious timeline. My advisor warned me that it was probably too aggressive, and he turned out to be right! You won't know things like this unless you discuss them with your advisor and committee, so keep that dialog going.
- Stay healthy. For me this means regular exercise, drinking enough water, eating healthy most of the time, getting enough sleep, and having some social interaction. When I was younger, my natural inclinations were to be much less healthy, but having an accountability partner makes it much easier to maintain these as habits. In my case, my wife is the person who helps me stick to the habits that I say I want to have, even when I might rather do something unhealthy. Without her, I am sure that I would be much less healthy and feel much worse.
- Find a balance that works for you. There are some people who can dive into research headfirst and be content never having interests or hobbies outside of that topic. If that works for you, I think that's fine. But to sustain my own wellbeing, I found it essential to do something completely different from time to time. Within the high-tech world, my research topic involves machine learning and reverse engineering. But I also enjoy learning about different programming languages (especially certain array-oriented languages), so when my brain demands taking a break from my main focus, I would do some recreational programming or puzzle solving in these other languages. Outside of high-tech, I found a lot of enjoyment in hand tool woodworking. The sounds, smells, and textures of carving, sawing, and planing wood into different shapes is a great way for me to de-stress. There's also something I find uniquely satisfying about building a usable physical object with my hands. Having a few of these kinds of non-research activities helps me recharge.
I shared these articles frequently with my Ph.D. peers.
- Ph.D. Proposal Advice from Matt Might. Without reading this article, I probably would have treated my research proposal more like a summary of what I had done so far, and a vague idea about what I wanted to do next. But with this article as a framework, I was able to craft a research proposal that was concrete and specific.
- Tips for Ph.D. Students also from Matt Might. Similar kinds of advice to the first post by the same author, but aimed at the graduate experience overall.
- A Survival Guide to a PhD by Andrej Karpathy. Andrej shares some outstandingly approachable content about machine learning on GitHub and YouTube. Especially pay attention to the section about Writing Papers. He makes a great point that while reading published papers may seem like a good way to learn how to write publish-worthy papers, if you only read what was published you end up training yourself as a binary classifier that only sees positive examples. If you also review papers before they've been published, you're much more likely to see negative examples that would not be accepted. Reviewing papers for journals or conferences is a good way to get this exposure, but don't neglect your own lab mates! Whenever I review a draft by a peer I usually find at least 1-2 typos and awkwardly phrased sentences per page (even if they use spell and grammar checking). Likewise, anytime someone reviews my drafts they always find something I missed. So go beta test those papers!