> Yes, "show me the github" is one of the worst trends for software developers' careers.
On the other hand, there are benefits to posting code online that they can review. Instead of spending hours writing code for each company that you're interviewing with, you can just write code that you're actually interested in and throw it online.
Say you're talking with 20 companies. Each of those 20 interviews have an associated overhead of 3 hours (if you're lucky): 1 hour screening call, 1 hour technical call, 1 hour live coding call. So 60 hours of screening, versus writing some code that might actually be usable by others in the future.
Don't be afraid to say no to live coding interviews. Unless you have nothing to show :-).
Some people are completely useless. Remember, there are people out there who can't write Fizz Buzz yet still apply for jobs. They can easily fake a GitHub.
Someone who won't write code upon request is an instant no-hire.
> Some people are completely useless. Remember, there are people out there who can't write Fizz Buzz yet still apply for jobs. They can easily fake a GitHub.
So you're saying they can use git-filter-branch, but not write Fizz Buzz? Sounds fishy to me.
>Instead of spending hours writing code for each company that you're interviewing with, you can just write code that you're actually interested in and throw it online.
Maybe, but I bet you'll still have to spend hours writing to code in order to prove that you wrote and understand the code, rather than copying it.
"... there are benefits to posting code online that they can review..."
In most domains, code is proprietary. Few ask for code samples because unscrupulous interviewees could reveal proprietary code, potentially opening the company to legal liabilities.
I make it a point not to read code that interviewees supply because I don't want to be sued by XYZ company because of code theft. In my industry, it has happened many times. Google "Sergey Aleynikov" and "Misha Malyshev" for an example of what can happen.
Comments
> Yes, "show me the github" is one of the worst trends for software developers' careers.
On the other hand, there are benefits to posting code online that they can review. Instead of spending hours writing code for each company that you're interviewing with, you can just write code that you're actually interested in and throw it online.
Say you're talking with 20 companies. Each of those 20 interviews have an associated overhead of 3 hours (if you're lucky): 1 hour screening call, 1 hour technical call, 1 hour live coding call. So 60 hours of screening, versus writing some code that might actually be usable by others in the future.
Don't be afraid to say no to live coding interviews. Unless you have nothing to show :-).
Some people are completely useless. Remember, there are people out there who can't write Fizz Buzz yet still apply for jobs. They can easily fake a GitHub.
Someone who won't write code upon request is an instant no-hire.
> Some people are completely useless. Remember, there are people out there who can't write Fizz Buzz yet still apply for jobs. They can easily fake a GitHub.
So you're saying they can use git-filter-branch, but not write Fizz Buzz? Sounds fishy to me.
>Instead of spending hours writing code for each company that you're interviewing with, you can just write code that you're actually interested in and throw it online.
Maybe, but I bet you'll still have to spend hours writing to code in order to prove that you wrote and understand the code, rather than copying it.
"... there are benefits to posting code online that they can review..."
In most domains, code is proprietary. Few ask for code samples because unscrupulous interviewees could reveal proprietary code, potentially opening the company to legal liabilities.
I make it a point not to read code that interviewees supply because I don't want to be sued by XYZ company because of code theft. In my industry, it has happened many times. Google "Sergey Aleynikov" and "Misha Malyshev" for an example of what can happen.
The common thread of this sample (N=2) seems to be that they are Russian.
Therefore, don't interview any Russians and you should be safe!