|
This might be a hint that this is not the company for you. I would tell them that you don't code as a hobby anymore and you don't have GitHub code. In my opinion, any quality technical interviewer can ask questions and determine your skill level and if you'd fit into their organization or not. I've been in my current position for 5.5 years and got it during a 1.5 hour interview. Today, the same level position requires a 8 hour test/program/interview. I would not consider my current position if I had to take a day off work for the opportunity for a new position.
|
|
|
|
|
jgakenhe wrote: would not consider my current position if I had to take a day off work for the opportunity for a new position.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
Tell them what you have told us.
If you are really keen on getting the job, you could also suggest that they set you a small project that would take no longer than a day to code then send back the resulting code to them.
I say this because I really dislike coding tests in interviews and have always done really well when I am set something in advance that I can then be questioned about during interview.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
GuyThiebaut wrote: you could also suggest that they set you a small project that would take no longer than a day to code
I like that idea. I'll float it at them and see what happens.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Never been asked that and at best I could point them here.
And definitely don't show code that another employer owns.
|
|
|
|
|
1. Imagine you owned the company you are interviewing for and you're interviewing a programmer.
2. Imagine you knew that the code is a representation of the actual business itself -- via business processes, etc.
3. Imagine that when the developer wrote the code that s/he would own a part of the business itself via owning the business processes it represents.
4. Imagine that the developer could walk out at any time leave behind a mess of business process behind that some other poor unfortunate would have to maintain.
5. Imagine your business might lose time, customers, and/or money because of that.
Now, what questions would you ask? 
|
|
|
|
|
I always try to leave documentation, standards, and well-commented code behind. My purpose isn't job security, it's to make sure that the next programmer does not face the same mess I walked into.
|
|
|
|
|
What everybody else said.
Don't try to "cover up" the fact that you've never used GitHub until now - the full history, with dates, is available, so they'll be able to tell you've hurriedly thrown something together for them to look at.
I'd have no problem telling any potential employer I don't have a GitHub account. Or that I used to have one at a previous employer...but that code is theirs.
|
|
|
|
|
Oh, I use GitHub for work, just not for personal code. Otherwise, yeah, I agree.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Simply point them to the articles you have written for CP.
Or tell them that you sell your code - how much are they willing to pay for it?
|
|
|
|
|
Er, I come to CP to read the buggers, not write them.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
I did that, got the job!
|
|
|
|
|
I have a "portfolio" that includes code I've written for my employer and from my outside projects. I don't have any qualms about sharing bits and pieces of code from my employer, as it is only intended to illustrate my programming style.
Software Zen: delete this;
|
|
|
|
|
I too do not have a GIT (yuck) repository. However, I do share my CP profile if someone wants. Apart from this I have a library of things that I simply copy and paste to applications I work with. For instance, encryption utilities, hashing utilities, basic REST API scaffolding. If they are hell bent and you too are for the job, I might just dump it all somewhere and share.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
Tell them you would show them after they showed you some examples of people they hired in their hobby time.
If you have to prove how much you like your job outside of work hours, then HR should at least do the same for you.
|
|
|
|
|
Awesome!
|
|
|
|
|
While that would be satisfying, I don't think it would win me any points. Besides, I am being contacted by the head of the IT department I'd be working for, and arranging the interview with his assistant. Looks like HR isn't involved for this one.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
I recently was asked to sit a sit a proprietary test at hackerrank [^]. I didn’t get around to it yet but I found that the training section has some good, short challenges that might be a good way of demonstrating your coding style and approach without the tedium of running your own project.
Good luck!
|
|
|
|
|
I've tried rewriting some of my code, but ended up telling the people that interviewed me that all of my work is done for a client and that I'm not able to share it with 3rd party. To my surprise, they were happy enough with my answer and told me that even they don't have it.
Keep in mind that for this to work, you will have to make good impression in the rest of the interview process.
|
|
|
|
|
In this case I think I would
* try to find code from my current job unrelated to business logic, more like library utilities, print it, and say that you cannot leave it with them
* talk to the interviewer on the phone about my predicament.
Chances are, you are up against hordes of kids with github repos galore. It could happen that they are spoiled with easily comparable candidates...
I was 52 when I got my current job, I think without my github I wouldnt be here.
... such stuff as dreams are made on
|
|
|
|
|
1) Create a repo on GitHub
2) Upload the following project
public class Program
{
static void Main(string[] args)
{
Console.WriteLine("Hello, world!");
}
}
3) Include it in your application
4) Profit
|
|
|
|
|
Oh yeah, there's the ticket. I could wow them even more by writing that in all the languages I know -- JavaScript, VB.NET, T-SQL, PL/SQL, PHP ...
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Do not, under any circumstances, give any code for a previous employer.
Doing that is asking for trouble and may even be a trick question to see if you are reliable security
person.
If they cannot assess your abilities from the interview ,this does not speak highly for the company you applied to. If the interview went without anyone fron the SW Dept. being present
is also a bad indicator.
all in all, probably a bad employer.
|
|
|
|
|
I think I'm being interviewed by the head of the IT department.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
TNCaver wrote: Everything I've done in the last 15 years that the interviewer would be interested in is proprietary code I've written for my current employer, and I don't feel comfortable sharing that outside the company
Put it on a stick, show it during the interview. No copies, they don't need the entire code-base to judge your skills - a minute worth of browsing would do.
Then ask them if you should keep their code on a public github 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
