Should I include my Github page on my resume?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
38
down vote
favorite
I am looking to become a developer and while I have been studying I have made a Github page and have filled it mostly with scripts or simple games that I have made plus a couple basic web applications.
Simply put, should I list my Github page on my resume as it is, or should I only include it if it contains something impressive (for example, consisting of many classes and/or being measured in the thousands of LOC as opposed to the hundreds)?
I guess I want to show that I do script and program in my own time, but I don't know if the simplicity of these scripts/apps are expected, or if they'd be a negative.
resume software-industry work-experience
edited May 15 '14 at 15:03
Oded
21.3k57898
asked May 15 '14 at 15:00
pi31415
90231117
add a comment |
up vote
38
down vote
favorite
I am looking to become a developer and while I have been studying I have made a Github page and have filled it mostly with scripts or simple games that I have made plus a couple basic web applications.
Simply put, should I list my Github page on my resume as it is, or should I only include it if it contains something impressive (for example, consisting of many classes and/or being measured in the thousands of LOC as opposed to the hundreds)?
I guess I want to show that I do script and program in my own time, but I don't know if the simplicity of these scripts/apps are expected, or if they'd be a negative.
resume software-industry work-experience
edited May 15 '14 at 15:03
Oded
21.3k57898
asked May 15 '14 at 15:00
pi31415
90231117
1
What do you name your projects? Maybe get a directory with Free_time_simple_scripts or something like that.
– Kevin
May 15 '14 at 15:06
4
If the code isn't terrible: YES.
– Joel Etherton
May 15 '14 at 18:01
2
Already some good answers, but I think it is worth mentioning simplicity -> complexity is not that important. Readability of the code, sensible comments, variable names and appropriate documentation are what will stand out. Automated tests are a good sign too. That doesn't mean you should spend hours polishing a small script, but do take a second look every now and then, and at least make it tidy and all comments accurate.
– Neil Slater
May 15 '14 at 19:58
1
This article discusses why Github isn't your CV, your question is about GH as part of it, but still an interesting read.
– rath
May 25 '14 at 13:12
add a comment |
up vote
38
down vote
favorite
up vote
38
down vote
favorite
I am looking to become a developer and while I have been studying I have made a Github page and have filled it mostly with scripts or simple games that I have made plus a couple basic web applications.
Simply put, should I list my Github page on my resume as it is, or should I only include it if it contains something impressive (for example, consisting of many classes and/or being measured in the thousands of LOC as opposed to the hundreds)?
I guess I want to show that I do script and program in my own time, but I don't know if the simplicity of these scripts/apps are expected, or if they'd be a negative.
resume software-industry work-experience
edited May 15 '14 at 15:03
Oded
21.3k57898
asked May 15 '14 at 15:00
pi31415
90231117
I am looking to become a developer and while I have been studying I have made a Github page and have filled it mostly with scripts or simple games that I have made plus a couple basic web applications.
Simply put, should I list my Github page on my resume as it is, or should I only include it if it contains something impressive (for example, consisting of many classes and/or being measured in the thousands of LOC as opposed to the hundreds)?
I guess I want to show that I do script and program in my own time, but I don't know if the simplicity of these scripts/apps are expected, or if they'd be a negative.
resume software-industry work-experience
resume software-industry work-experience
edited May 15 '14 at 15:03
Oded
21.3k57898
asked May 15 '14 at 15:00
pi31415
90231117
edited May 15 '14 at 15:03
Oded
21.3k57898
asked May 15 '14 at 15:00
pi31415
90231117
edited May 15 '14 at 15:03
Oded
21.3k57898
edited May 15 '14 at 15:03
Oded
21.3k57898
edited May 15 '14 at 15:03
Oded
21.3k57898
21.3k57898
asked May 15 '14 at 15:00
pi31415
90231117
asked May 15 '14 at 15:00
pi31415
90231117
asked May 15 '14 at 15:00
pi31415
90231117
90231117
1
What do you name your projects? Maybe get a directory with Free_time_simple_scripts or something like that.
– Kevin
May 15 '14 at 15:06
4
If the code isn't terrible: YES.
– Joel Etherton
May 15 '14 at 18:01
2
Already some good answers, but I think it is worth mentioning simplicity -> complexity is not that important. Readability of the code, sensible comments, variable names and appropriate documentation are what will stand out. Automated tests are a good sign too. That doesn't mean you should spend hours polishing a small script, but do take a second look every now and then, and at least make it tidy and all comments accurate.
– Neil Slater
May 15 '14 at 19:58
1
This article discusses why Github isn't your CV, your question is about GH as part of it, but still an interesting read.
– rath
May 25 '14 at 13:12
add a comment |
1
What do you name your projects? Maybe get a directory with Free_time_simple_scripts or something like that.
– Kevin
May 15 '14 at 15:06
4
If the code isn't terrible: YES.
– Joel Etherton
May 15 '14 at 18:01
2
Already some good answers, but I think it is worth mentioning simplicity -> complexity is not that important. Readability of the code, sensible comments, variable names and appropriate documentation are what will stand out. Automated tests are a good sign too. That doesn't mean you should spend hours polishing a small script, but do take a second look every now and then, and at least make it tidy and all comments accurate.
– Neil Slater
May 15 '14 at 19:58
1
This article discusses why Github isn't your CV, your question is about GH as part of it, but still an interesting read.
– rath
May 25 '14 at 13:12
1
1
What do you name your projects? Maybe get a directory with Free_time_simple_scripts or something like that.
– Kevin
May 15 '14 at 15:06
What do you name your projects? Maybe get a directory with Free_time_simple_scripts or something like that.
– Kevin
May 15 '14 at 15:06
4
4
If the code isn't terrible: YES.
– Joel Etherton
May 15 '14 at 18:01
If the code isn't terrible: YES.
– Joel Etherton
May 15 '14 at 18:01
2
2
Already some good answers, but I think it is worth mentioning simplicity -> complexity is not that important. Readability of the code, sensible comments, variable names and appropriate documentation are what will stand out. Automated tests are a good sign too. That doesn't mean you should spend hours polishing a small script, but do take a second look every now and then, and at least make it tidy and all comments accurate.
– Neil Slater
May 15 '14 at 19:58
Already some good answers, but I think it is worth mentioning simplicity -> complexity is not that important. Readability of the code, sensible comments, variable names and appropriate documentation are what will stand out. Automated tests are a good sign too. That doesn't mean you should spend hours polishing a small script, but do take a second look every now and then, and at least make it tidy and all comments accurate.
– Neil Slater
May 15 '14 at 19:58
1
1
This article discusses why Github isn't your CV, your question is about GH as part of it, but still an interesting read.
– rath
May 25 '14 at 13:12
This article discusses why Github isn't your CV, your question is about GH as part of it, but still an interesting read.
– rath
May 25 '14 at 13:12
add a comment |
4 Answers
4
active
oldest
votes
up vote
41
down vote
accepted
If you are happy with the code, then it always helps to publish it. I'm a hiring manager for engineers, and even if the project isn't impressive, I'd like to browse it to get a sense of:
If the engineer has enough internal motivation to publish side
projectsIf the code seems to follow most best practices. I won't
have to teach the engineer best practices if they join my teamLooking for good clean well tested code.
If you're proud of it, include the link!
edited May 15 '14 at 18:59
Matt
1034
answered May 15 '14 at 15:04
PMiller
43955
add a comment |
up vote
15
down vote
You should.
Your github repository is the only evidence that's available to them that you can write or design anything. Yes, your github contents could use improvement. I put mine up as a motivator to me to improve on my software engineering capabilities. My github is woefully out of date but I get a kick out of seeing where I am compared to where I was. Showing something is better than showing nothing, as long that the something that you show is a positive, like your competence :)
Plus, your github link is your way of saying that you know how to use github. Actually, I had to learn the github internals to do that but that'sanother story for another day. At the very least,publishing your github account should motivate you to learn as much as you can about github. There is no uch thing as being too good at github :)
Being a good software engineer is a process not a termination point to a process. As you improve and get to be wylier as a problem solver, your github contents become more sophisticated. And no, the process doesn't have an end point :)
In terms of what to publish, code that highlights your grip on the fundamentals is fine. Junk is not. The line between good stuff and junk can be blurry. My standard is that I don't publish anything that I cannot justify as publishable.
answered May 15 '14 at 15:15
Vietnhi Phuvan
69.1k7119255
add a comment |
up vote
5
down vote
If you were interviewing at my company, we'd ask you if you had a github account (or some other public code repository) quite early in the hiring process.
Depending on your responsibilities we'd then look for specific traits (actually more the absence of undesirable traits) so that we'd get a feeling of
- your actual capabilities versus your claimed experiences
- how much training would be necessary to integrate you into a project team
So, along with my predecessors, I strongly recommend including it.
Edit 04/2016: re Undesirable traits
Happy coincidence ... just a few days ago I came upon this piece, which nicely sums this up for the "programmer" side of employees.
On the "personality" level ... difficult to say without getting into a lengthy monologue. Recently one of my clients complimented me on how I always manage to project calmness and listen to them, think about problems before presenting a solution, while other consultants "just want to do their thing" and charge heavily. To which I replied "I left my ego tied up in the trunk outside in the parking lot". They have also heard "I don't know, I have to look it up", "Interesting problem, let me experiment a bit, no charge", "I could do that but if you just buy X, you'll be better off" from me.
TL;DR: rock stars, code ninjas, pure tech wizards: no. Generally Competent Human: yes.
answered May 15 '14 at 17:52
Stefan Schmiedl
38136
Hi, can you share with us some of these undesirable traits?
– user308553
Apr 4 '16 at 16:49
add a comment |
up vote
0
down vote
I say yes. As a technical lead who also does interviews, I like to see people's code and honestly, I'm not looking for quality code, though that would be noted if it was the case. It's more about: Can you get better? Can you learn? Can you grow? For me, the ideal repository is a one that starts with a really old, poorly done calculator app and then the latest commit being some personal passion project with multiple layers of complexity. It doesn't need to be perfect or good. I just need to see if you can grow. The ideal candidate is a candidate who is extremely responsive to change, and isn't afraid to learn new things.
answered Nov 30 at 12:38
ShinEmperor
1,11726
New contributor
ShinEmperor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
StackExchange.ready(function () {
$("#show-editor-button input, #show-editor-button button").click(function () {
var showEditor = function() {
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
};
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True') {
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup({
url: '/post/self-answer-popup',
loaded: function(popup) {
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
}
})
} else{
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true) {
showEditor();
}
}
});
});
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
41
down vote
accepted
If you are happy with the code, then it always helps to publish it. I'm a hiring manager for engineers, and even if the project isn't impressive, I'd like to browse it to get a sense of:
If the engineer has enough internal motivation to publish side
projectsIf the code seems to follow most best practices. I won't
have to teach the engineer best practices if they join my teamLooking for good clean well tested code.
If you're proud of it, include the link!
edited May 15 '14 at 18:59
Matt
1034
answered May 15 '14 at 15:04
PMiller
43955
add a comment |
up vote
41
down vote
accepted
If you are happy with the code, then it always helps to publish it. I'm a hiring manager for engineers, and even if the project isn't impressive, I'd like to browse it to get a sense of:
If the engineer has enough internal motivation to publish side
projectsIf the code seems to follow most best practices. I won't
have to teach the engineer best practices if they join my teamLooking for good clean well tested code.
If you're proud of it, include the link!
edited May 15 '14 at 18:59
Matt
1034
answered May 15 '14 at 15:04
PMiller
43955
add a comment |
up vote
41
down vote
accepted
up vote
41
down vote
accepted
If you are happy with the code, then it always helps to publish it. I'm a hiring manager for engineers, and even if the project isn't impressive, I'd like to browse it to get a sense of:
If the engineer has enough internal motivation to publish side
projectsIf the code seems to follow most best practices. I won't
have to teach the engineer best practices if they join my teamLooking for good clean well tested code.
If you're proud of it, include the link!
edited May 15 '14 at 18:59
Matt
1034
answered May 15 '14 at 15:04
PMiller
43955
If you are happy with the code, then it always helps to publish it. I'm a hiring manager for engineers, and even if the project isn't impressive, I'd like to browse it to get a sense of:
If the engineer has enough internal motivation to publish side
projectsIf the code seems to follow most best practices. I won't
have to teach the engineer best practices if they join my teamLooking for good clean well tested code.
If you're proud of it, include the link!
edited May 15 '14 at 18:59
Matt
1034
answered May 15 '14 at 15:04
PMiller
43955
edited May 15 '14 at 18:59
Matt
1034
edited May 15 '14 at 18:59
Matt
1034
edited May 15 '14 at 18:59
Matt
1034
1034
answered May 15 '14 at 15:04
PMiller
43955
answered May 15 '14 at 15:04
PMiller
43955
answered May 15 '14 at 15:04
PMiller
43955
43955
add a comment |
add a comment |
up vote
15
down vote
You should.
Your github repository is the only evidence that's available to them that you can write or design anything. Yes, your github contents could use improvement. I put mine up as a motivator to me to improve on my software engineering capabilities. My github is woefully out of date but I get a kick out of seeing where I am compared to where I was. Showing something is better than showing nothing, as long that the something that you show is a positive, like your competence :)
Plus, your github link is your way of saying that you know how to use github. Actually, I had to learn the github internals to do that but that'sanother story for another day. At the very least,publishing your github account should motivate you to learn as much as you can about github. There is no uch thing as being too good at github :)
Being a good software engineer is a process not a termination point to a process. As you improve and get to be wylier as a problem solver, your github contents become more sophisticated. And no, the process doesn't have an end point :)
In terms of what to publish, code that highlights your grip on the fundamentals is fine. Junk is not. The line between good stuff and junk can be blurry. My standard is that I don't publish anything that I cannot justify as publishable.
answered May 15 '14 at 15:15
Vietnhi Phuvan
69.1k7119255
add a comment |
up vote
15
down vote
You should.
Your github repository is the only evidence that's available to them that you can write or design anything. Yes, your github contents could use improvement. I put mine up as a motivator to me to improve on my software engineering capabilities. My github is woefully out of date but I get a kick out of seeing where I am compared to where I was. Showing something is better than showing nothing, as long that the something that you show is a positive, like your competence :)
Plus, your github link is your way of saying that you know how to use github. Actually, I had to learn the github internals to do that but that'sanother story for another day. At the very least,publishing your github account should motivate you to learn as much as you can about github. There is no uch thing as being too good at github :)
Being a good software engineer is a process not a termination point to a process. As you improve and get to be wylier as a problem solver, your github contents become more sophisticated. And no, the process doesn't have an end point :)
In terms of what to publish, code that highlights your grip on the fundamentals is fine. Junk is not. The line between good stuff and junk can be blurry. My standard is that I don't publish anything that I cannot justify as publishable.
answered May 15 '14 at 15:15
Vietnhi Phuvan
69.1k7119255
add a comment |
up vote
15
down vote
up vote
15
down vote
You should.
Your github repository is the only evidence that's available to them that you can write or design anything. Yes, your github contents could use improvement. I put mine up as a motivator to me to improve on my software engineering capabilities. My github is woefully out of date but I get a kick out of seeing where I am compared to where I was. Showing something is better than showing nothing, as long that the something that you show is a positive, like your competence :)
Plus, your github link is your way of saying that you know how to use github. Actually, I had to learn the github internals to do that but that'sanother story for another day. At the very least,publishing your github account should motivate you to learn as much as you can about github. There is no uch thing as being too good at github :)
Being a good software engineer is a process not a termination point to a process. As you improve and get to be wylier as a problem solver, your github contents become more sophisticated. And no, the process doesn't have an end point :)
In terms of what to publish, code that highlights your grip on the fundamentals is fine. Junk is not. The line between good stuff and junk can be blurry. My standard is that I don't publish anything that I cannot justify as publishable.
answered May 15 '14 at 15:15
Vietnhi Phuvan
69.1k7119255
You should.
Your github repository is the only evidence that's available to them that you can write or design anything. Yes, your github contents could use improvement. I put mine up as a motivator to me to improve on my software engineering capabilities. My github is woefully out of date but I get a kick out of seeing where I am compared to where I was. Showing something is better than showing nothing, as long that the something that you show is a positive, like your competence :)
Plus, your github link is your way of saying that you know how to use github. Actually, I had to learn the github internals to do that but that'sanother story for another day. At the very least,publishing your github account should motivate you to learn as much as you can about github. There is no uch thing as being too good at github :)
Being a good software engineer is a process not a termination point to a process. As you improve and get to be wylier as a problem solver, your github contents become more sophisticated. And no, the process doesn't have an end point :)
In terms of what to publish, code that highlights your grip on the fundamentals is fine. Junk is not. The line between good stuff and junk can be blurry. My standard is that I don't publish anything that I cannot justify as publishable.
answered May 15 '14 at 15:15
Vietnhi Phuvan
69.1k7119255
answered May 15 '14 at 15:15
Vietnhi Phuvan
69.1k7119255
answered May 15 '14 at 15:15
Vietnhi Phuvan
69.1k7119255
answered May 15 '14 at 15:15
Vietnhi Phuvan
69.1k7119255
69.1k7119255
add a comment |
add a comment |
up vote
5
down vote
If you were interviewing at my company, we'd ask you if you had a github account (or some other public code repository) quite early in the hiring process.
Depending on your responsibilities we'd then look for specific traits (actually more the absence of undesirable traits) so that we'd get a feeling of
- your actual capabilities versus your claimed experiences
- how much training would be necessary to integrate you into a project team
So, along with my predecessors, I strongly recommend including it.
Edit 04/2016: re Undesirable traits
Happy coincidence ... just a few days ago I came upon this piece, which nicely sums this up for the "programmer" side of employees.
On the "personality" level ... difficult to say without getting into a lengthy monologue. Recently one of my clients complimented me on how I always manage to project calmness and listen to them, think about problems before presenting a solution, while other consultants "just want to do their thing" and charge heavily. To which I replied "I left my ego tied up in the trunk outside in the parking lot". They have also heard "I don't know, I have to look it up", "Interesting problem, let me experiment a bit, no charge", "I could do that but if you just buy X, you'll be better off" from me.
TL;DR: rock stars, code ninjas, pure tech wizards: no. Generally Competent Human: yes.
answered May 15 '14 at 17:52
Stefan Schmiedl
38136
Hi, can you share with us some of these undesirable traits?
– user308553
Apr 4 '16 at 16:49
add a comment |
up vote
5
down vote
If you were interviewing at my company, we'd ask you if you had a github account (or some other public code repository) quite early in the hiring process.
Depending on your responsibilities we'd then look for specific traits (actually more the absence of undesirable traits) so that we'd get a feeling of
- your actual capabilities versus your claimed experiences
- how much training would be necessary to integrate you into a project team
So, along with my predecessors, I strongly recommend including it.
Edit 04/2016: re Undesirable traits
Happy coincidence ... just a few days ago I came upon this piece, which nicely sums this up for the "programmer" side of employees.
On the "personality" level ... difficult to say without getting into a lengthy monologue. Recently one of my clients complimented me on how I always manage to project calmness and listen to them, think about problems before presenting a solution, while other consultants "just want to do their thing" and charge heavily. To which I replied "I left my ego tied up in the trunk outside in the parking lot". They have also heard "I don't know, I have to look it up", "Interesting problem, let me experiment a bit, no charge", "I could do that but if you just buy X, you'll be better off" from me.
TL;DR: rock stars, code ninjas, pure tech wizards: no. Generally Competent Human: yes.
answered May 15 '14 at 17:52
Stefan Schmiedl
38136
Hi, can you share with us some of these undesirable traits?
– user308553
Apr 4 '16 at 16:49
add a comment |
up vote
5
down vote
up vote
5
down vote
If you were interviewing at my company, we'd ask you if you had a github account (or some other public code repository) quite early in the hiring process.
Depending on your responsibilities we'd then look for specific traits (actually more the absence of undesirable traits) so that we'd get a feeling of
- your actual capabilities versus your claimed experiences
- how much training would be necessary to integrate you into a project team
So, along with my predecessors, I strongly recommend including it.
Edit 04/2016: re Undesirable traits
Happy coincidence ... just a few days ago I came upon this piece, which nicely sums this up for the "programmer" side of employees.
On the "personality" level ... difficult to say without getting into a lengthy monologue. Recently one of my clients complimented me on how I always manage to project calmness and listen to them, think about problems before presenting a solution, while other consultants "just want to do their thing" and charge heavily. To which I replied "I left my ego tied up in the trunk outside in the parking lot". They have also heard "I don't know, I have to look it up", "Interesting problem, let me experiment a bit, no charge", "I could do that but if you just buy X, you'll be better off" from me.
TL;DR: rock stars, code ninjas, pure tech wizards: no. Generally Competent Human: yes.
answered May 15 '14 at 17:52
Stefan Schmiedl
38136
If you were interviewing at my company, we'd ask you if you had a github account (or some other public code repository) quite early in the hiring process.
Depending on your responsibilities we'd then look for specific traits (actually more the absence of undesirable traits) so that we'd get a feeling of
- your actual capabilities versus your claimed experiences
- how much training would be necessary to integrate you into a project team
So, along with my predecessors, I strongly recommend including it.
Edit 04/2016: re Undesirable traits
Happy coincidence ... just a few days ago I came upon this piece, which nicely sums this up for the "programmer" side of employees.
On the "personality" level ... difficult to say without getting into a lengthy monologue. Recently one of my clients complimented me on how I always manage to project calmness and listen to them, think about problems before presenting a solution, while other consultants "just want to do their thing" and charge heavily. To which I replied "I left my ego tied up in the trunk outside in the parking lot". They have also heard "I don't know, I have to look it up", "Interesting problem, let me experiment a bit, no charge", "I could do that but if you just buy X, you'll be better off" from me.
TL;DR: rock stars, code ninjas, pure tech wizards: no. Generally Competent Human: yes.
answered May 15 '14 at 17:52
Stefan Schmiedl
38136
edited Apr 5 '16 at 18:07
answered May 15 '14 at 17:52
Stefan Schmiedl
38136
answered May 15 '14 at 17:52
Stefan Schmiedl
38136
answered May 15 '14 at 17:52
Stefan Schmiedl
38136
38136
Hi, can you share with us some of these undesirable traits?
– user308553
Apr 4 '16 at 16:49
add a comment |
Hi, can you share with us some of these undesirable traits?
– user308553
Apr 4 '16 at 16:49
Hi, can you share with us some of these undesirable traits?
– user308553
Apr 4 '16 at 16:49
Hi, can you share with us some of these undesirable traits?
– user308553
Apr 4 '16 at 16:49
add a comment |
up vote
0
down vote
I say yes. As a technical lead who also does interviews, I like to see people's code and honestly, I'm not looking for quality code, though that would be noted if it was the case. It's more about: Can you get better? Can you learn? Can you grow? For me, the ideal repository is a one that starts with a really old, poorly done calculator app and then the latest commit being some personal passion project with multiple layers of complexity. It doesn't need to be perfect or good. I just need to see if you can grow. The ideal candidate is a candidate who is extremely responsive to change, and isn't afraid to learn new things.
answered Nov 30 at 12:38
ShinEmperor
1,11726
New contributor
ShinEmperor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
I say yes. As a technical lead who also does interviews, I like to see people's code and honestly, I'm not looking for quality code, though that would be noted if it was the case. It's more about: Can you get better? Can you learn? Can you grow? For me, the ideal repository is a one that starts with a really old, poorly done calculator app and then the latest commit being some personal passion project with multiple layers of complexity. It doesn't need to be perfect or good. I just need to see if you can grow. The ideal candidate is a candidate who is extremely responsive to change, and isn't afraid to learn new things.
answered Nov 30 at 12:38
ShinEmperor
1,11726
New contributor
ShinEmperor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
I say yes. As a technical lead who also does interviews, I like to see people's code and honestly, I'm not looking for quality code, though that would be noted if it was the case. It's more about: Can you get better? Can you learn? Can you grow? For me, the ideal repository is a one that starts with a really old, poorly done calculator app and then the latest commit being some personal passion project with multiple layers of complexity. It doesn't need to be perfect or good. I just need to see if you can grow. The ideal candidate is a candidate who is extremely responsive to change, and isn't afraid to learn new things.
answered Nov 30 at 12:38
ShinEmperor
1,11726
New contributor
ShinEmperor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I say yes. As a technical lead who also does interviews, I like to see people's code and honestly, I'm not looking for quality code, though that would be noted if it was the case. It's more about: Can you get better? Can you learn? Can you grow? For me, the ideal repository is a one that starts with a really old, poorly done calculator app and then the latest commit being some personal passion project with multiple layers of complexity. It doesn't need to be perfect or good. I just need to see if you can grow. The ideal candidate is a candidate who is extremely responsive to change, and isn't afraid to learn new things.
answered Nov 30 at 12:38
ShinEmperor
1,11726
New contributor
ShinEmperor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 30 at 12:38
ShinEmperor
1,11726
New contributor
ShinEmperor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 30 at 12:38
ShinEmperor
1,11726
answered Nov 30 at 12:38
ShinEmperor
1,11726
1,11726
New contributor
ShinEmperor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
ShinEmperor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
ShinEmperor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f24128%2fshould-i-include-my-github-page-on-my-resume%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
What do you name your projects? Maybe get a directory with Free_time_simple_scripts or something like that.
– Kevin
May 15 '14 at 15:06
4
If the code isn't terrible: YES.
– Joel Etherton
May 15 '14 at 18:01
2
Already some good answers, but I think it is worth mentioning simplicity -> complexity is not that important. Readability of the code, sensible comments, variable names and appropriate documentation are what will stand out. Automated tests are a good sign too. That doesn't mean you should spend hours polishing a small script, but do take a second look every now and then, and at least make it tidy and all comments accurate.
– Neil Slater
May 15 '14 at 19:58
1
This article discusses why Github isn't your CV, your question is about GH as part of it, but still an interesting read.
– rath
May 25 '14 at 13:12