You are currently viewing GitHub is the New Resume
GitHub Twitter Page

GitHub is the New Resume

  • Post author:
  • Post category:Technology

There are several technologies or processes that are a given in the current modern era of technology.  Cloud, AI, Agile, DevOps, mobile, and security to name a few.  Git has become a given, replacing older technologies like subversion, CVS, ClearCase, Harvest, RCS, and SCCS.  While there are still many version control systems, Git has become a standard for most developers and companies.  And when you think of Git, you naturally think of GitHub, although they are technical not exactly the same thing.  See some articles explaining the difference:

GitHub was purchased by Microsoft in 2018 for $7.5 billion.  Even before this purchase, developers have been using GitHub to store their project code.  It has become so popular that many developers have their own personal accounts on github.com.  And now when you go to conferences, many of the presenters will have their content on github.com, slideshare.net, dropbox.com, google docs, or their own personal or corporate web site.  These presenters used to share their twitter handles or email addresses, but now they are even sharing their github URLs.  And recruiters are looking at their GitHub repositories for a sense of their technical abilities.  They may even ask you for your GitHub URL.  There is even some debate whether GitHub should be the literal source of your resume.  For example, see the Sidekick article on resumes and github.  But I am not talking about the use of GitHub as a resume.  I am talking about other people looking at your GitHub repository to check you out.  Your street creds, as some might say.

I was at the CodeMash conference recently, and I observed the attendees checking the GitHub repos of the presenters.  In the past, most people would check out their twitter feed, but now GitHub has become another way to learn about your technical comrades.  And they are putting more than code in their.  Using GitHub pages and Jekyll, you can publish documentation or other types of content.  Or you can just use the MarkDown capabilities of GitHub to create simple content.  Either way, GitHub becomes a source for both code and documentation.

I still see presentation slides being created using other tools, but GitHub can host those presentations.  Or you can use GitHub pages to create content.  There are some cool ways to create resumes on GitHub pages.  One example is techfolios.github.io.