FutureStarr

Github in Resume

Github in Resume

Github in Resume

via GIPHY

A few of us at CircleCI have been thinking about the role GitHub (Git) plays in our lives as software engineers. It can be time-consuming, tedious, and disheartening to keep everything up to date and in synch. But perhaps it is more valuable for its safety and security features.

GitHub

via GIPHY

Martin Poduska is a resume expert and career advice writer at Kickresume. He leads Kickresume’s team of writers and is the main person responsible for upholding the standards of expertise and quality on the blog. In addition to having written nearly 100 in-depth, painstakingly researched resume advice articles, as chief editor he has also edited and revised every single article on this blog. Tens of thousands of job seekers read Martin’s resume advice every month. Martin holds a degree in English from the University of St Andrews and a degree in Comparative Literature from the University of Amsterdam.

In this article, we will show you how to use GitHub in a way that you never thought could be used. You will learn how to use your GitHub profile as a resume (CV) or, even more, as a presentation site for yourself or your company. You will learn how to customize, in a very beautiful way, the first page that a user sees when he enters your GitHub profile. We will show you how you can display the repos you are most proud of, how to list your written articles, how to present your youtube channel, and much more. (Source: www.creative-tim.com)

Software

via GIPHY

Second, even if GitHub allowed you to control its presentation of your work, it still wouldn’t be a good signal. Various people have made the case that it’s your portfolio, in the sense that artists and designers use the term, that you should have a body of work to show off to employers (people like to make empty and easily falsifiable analogies between software engineering and other disciplines, mostly, as far as I can tell, to make themselves feel all warm and tingly). Here’s the thing: it’s not. A portfolio is an edited collection of professional and personal work that someone working in the visual arts uses to present their best face to possible clients. It’s a visual CV, and just like a CV its editing is tailored depending on who you’re trying to impress. GitHub is not this at all. GitHub is all the public work you’ve ever done, unordered, unfiltered and unexplained. It tells no story and provides no context.

And context is incredibly important. The reasons people put things on GitHub are many and varied: they just want a backup (git is literally the only software that has yet to lose my data), they want to collaborate, they like the issue tracker and pull requests, they want a hosted page for their project’s docs, it is their employer’s policy that all code is public. Personally, I use GitHub as a place to host serious long-term projects, as a sketch pad for experiments, as a backup system, and as a place for people to file bugs. Some of my projects are ‘normal’ practically useful software, some are build tools that support said projects, some are experiments that went nowhere, some are experiments I’m still working on, some are study projects, some are flights of intellectual curiosity, some are demos, some are instructive projects, some are jokes, and some are not even software. Some of my most-forked software took a week to write, and I’ve spent literally years on projects almost no-one cares about. (Source: blog.jcoglan.com)

Share

Assignments & Coursework: This may not be your highest quality work, but that doesn’t mean it is not worthy to be a part of your portfolio. All of the programming assignments and coursework you received at school or through courses are still valuable projects to have included but remember if 50,000 people took the same course and share the same thing then you’re going to have to do a bit more if you want to stand out.

Competitions: If you ever decide to participate in competitions then sharing how you faired is a great step. Although many feel as though competitions do not replicate real-world scenarios, I feel as though there is still plenty of value to take from them and they should definitely be included as part of your portfolio (It’s even better if you can rank high in the competition). (Source: towardsdatascience.com)

Related Articles