17 Things to Know Before Deciding to Get a Ph.D. in Computer Science
Tags: education, computerscience, career
Published: 2022-02-21 19:11:33

---
canonical_url: https://davidadamojr.com/lessons-from-5-5-years-working-on-a-computer-science-ph-d/
description: 17 things to know before deciding to get a Ph.D. in Computer Science
---
<!-- wp:paragraph -->
<p>This post is long overdue and marks the start of a series of blog posts about my journey through earning a Ph.D. in Computer Science.&nbsp;</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>On August 15, 2012, I moved to the United States of America to accept an offer of admission to a Computer Science Ph.D. program. The decision to pursue a Ph.D. in Computer Science marked the beginning of an arduous five-and-a-half-year journey of self-discovery and personal development. I eventually graduated in December 2017 and it has taken me a few years to settle into life outside of graduate school. <a href="http://davidadamojr.com/research/" title="Peer-Reviewed Publications" target="_blank">8 peer-reviewed publications</a>, <a href="https://scholar.google.com/citations?hl=en&amp;user=xA_KeHsAAAAJ" target="_blank" rel="noreferrer noopener" title="https://scholar.google.com/citations?hl=en&amp;user=xA_KeHsAAAAJ">7 patents</a>, and <a href="https://www.linkedin.com/in/davidadamojr/" target="_blank" title="https://www.linkedin.com/in/davidadamojr/">4 full-time software engineering jobs</a> later, I now have enough mental clarity to reflect on my time in graduate school and share what I wish I knew at the start of the Ph.D. journey.&nbsp;</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>Please note that the lessons shared in this post are colored by my particular experience in a Software Engineering-focused research area and at a specific university in the United States. Some of the things mentioned in this post may not apply to all countries, fields of study, and across all universities. Now, without further ado, here are 17 lessons learned in retrospect and things I wish I knew when I started the Ph.D. journey.</p>
<!-- /wp:paragraph -->

<!-- wp:list -->
<ul><li><a href="https://en.wikipedia.org/wiki/It_takes_a_village" target="_blank" rel="noreferrer noopener" title="https://en.wikipedia.org/wiki/It_takes_a_village">It takes a village</a> to earn a Ph.D.</li><li>Choose your advisor(s) wisely and carefully.</li><li>Be mindful of academic politics.</li><li>Avoid resource-intensive research areas.</li><li>Software development skill matters much less than you think.</li><li>Experiment design skill is more valuable than you think.</li><li>Write often and publish early.</li><li>You don't write as well as you think.</li><li>Grades matter less than you think.</li><li>Stay funded.</li><li>There is an alarming disconnect between academia and industry practice.</li><li>Teaching is difficult but sometimes rewarding.</li><li>The non-research career opportunity cost is real and often incredibly high.</li><li>Squash impostor syndrome often and early.</li><li>Professors are human too.</li><li>There are potential immigration advantages.</li><li>Do not get a Ph.D. 😊</li></ul>
<!-- /wp:list -->

<!-- wp:paragraph -->
<p>In subsequent posts, I will elaborate on each of these lessons. Each person's experience in a Computer Science Ph.D. program is unique, and one person's experience is not necessarily a reliable predictor of another's. Having said that, I hope that my experience and perspective on these topics will help people who may be considering a foray into the <a href="https://www.scholat.com/teamwork/teamworkdownloadscholar.html?id=4924&amp;teamId=1158" target="_blank" rel="noreferrer noopener" title="https://www.scholat.com/teamwork/teamworkdownloadscholar.html?id=4924&amp;teamId=1158">Ph.D. grind</a><sub>(pdf book)</sub>.</p>
<!-- /wp:paragraph -->