|
Excellent answer.
I routinely offer to send/show my personal projects, for the very reason you mentioned. It lets them know how I think and code, and moreover, it tells them that I can analyze problems and design complete solutions - not just write code.
If it's not broken, fix it until it is
|
|
|
|
|
Yes it is a good idea. I developed my own person website back around 2000 and used it for the next 10 years to market myself. I got one job in 2004 because I created tabs on a page and also had a portfolio page.
|
|
|
|
|
John Simmons / outlaw programmer wrote: Ask to see some of the candidates personal code (projects he works on in his own time).
I work for a living and have always done so.
The last time I did code for myself I had never been paid to program.
Since then the code I throw has always belonged to someone else.
Which mean I have absolutely no right to show it to anyone else.
|
|
|
|
|
I have also always worked for a living, but I spend a lot of time writing my own stuff. Occasionally, I develop some code for an employer and after getting permission, write an article about the techniques I developed in pursuit of the final code. I've found that most employers are fine with technology sharing unless the code in question is highly proprietary (exposes trade secrets, or is so unique and innovative as to expose the company to competitive loss).
I am honestly amazed at the number of programmers I've personally encountered that DON'T write code as a hobby at home. IMHO, it shows a lack of commitment to the art of development, but I also understand the necessity to separate private life from vocational pursuits. I'll always be more interested in hiring people that have a demonstrable passion for the act of writing code.
For my current job, I was interviewed by a PM who had no idea what to ask. No programming questions at all, just explanations of the code I worked on in the past. It was kind of a strange interview.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: I've personally encountered that DON'T write code as a hobby at home. IMHO, it shows a lack of commitment to the art of development,
For about 20 years I worked 60+ hour weeks and, where possible, would take vacation time as a bonus check rather than taking actual time off.
I know people who have worked more hours a week than that. For years.
My "hobby" was in fact writing code, but doing so for my employer.
|
|
|
|
|
I had that sort of interview for my first job out of school. About 50 programming questions and an hour to do them, it reminded me of a test in Comp Sci 101. Breezed through those and then had a short face to face interview with the team manager. The guy had been a DBA back when he started so had an idea of what questions to ask and what the reason and concept was behind the answer he wanted. They could have skipped the entire first bit and just go with the interview. Would have saved everyone's time. I can teach someone the syntax of a language. I cannot teach someone how to approach a problem or think for themselves.
After a number of years in, I tend to be able to get a better feel for someone's ability by asking questions about how they would approach a problem instead of what is the solution for that same problem. If your solution is overly complex, your code tends to be as well and will be a beast to maintain once you are gone. If you won't even attempt to solve think about it then you will be here on CodeProject and other various boards asking people how to do your work.
In my mind, how a developer thinks and learns is much more important than what they already claim to know.
|
|
|
|
|
This is a very important topic. One of my first IT interviews for an entry level position, I was asked the same question and didn't know that answer and no I didn't get the job. But subsequent interviews, I was ready for the Reverse String question.
An interview says a lot about the company. Today, if someone interviews me and have nonsense or irrelevant questions pertaining to my level or the level of the job, then I will not take the job. Additionally, it makes the company look bad. Why would I want to work for a backwards company?
|
|
|
|
|
Oh well, our interview process is pretty shambles, the senior developer that we had for the last 12 years (he's recently quit) was hired because back then he was the only one who turned up for the "interview" and he was interviewed by, shall we say, less than a programmer person. That's no blinkin' way to interview someone for a highly involved and skilled job!
This guy had an air of hollow superiority over every one else and was extremely condescending but he ended up working for 12 years and built a system that only he had any clue about. He had a horrible programming style and was routinely in habit of creating 100 line methods. May maintainability rest in peace!
Its clearly a proof of severely flawed hiring process that we have, funnily enough, prior to my interview at my current workplace more than 4 years ago, I was given a programming assignment that I had to complete and bring in and then walk the devs through my thinking process and understanding that eventually led to a solution. The focus wasn't on if I can solve the problem correctly but whether or not I can come up with approaches to solve the problem and convey my ideas to others. Why couldn't we have done something similar with this guy? I agree interviewing is hard but asking these stock questions is just plain lazy and condescending IMO.
|
|
|
|
|
I ask 5 (non-technical) questions. If they can't get through those then I know I wouldn't hire them as, no matter how good they may well be, they are not a cultural fit and are unlikely to fir into the team or stay very long.
You can be the moist brilliant developer in the world but if you don't fit on with the company culture, you won't last and that is a waste of everyone's time.
|
|
|
|
|
I.explore.code wrote: we had a candidate over for a "Junior Developer"...What is your opinion on this?
Depends on exactly what "junior developer" means.
A developer with no experience should not be expected to know anything about professional programming. A non-senior level developer, say with an expectation of 2-4 years of experience, should know something about programming.
I.explore.code wrote: not having done a job long enough,
Say what? You asked a candidate in for an interview knowing that they did have enough professional experience for the minimum job requirement?
That is unprofessional on the companies part.
I.explore.code wrote: Now that in my opinion is the failure of the interviewer
Sort of.
Fact of the matter is to correctly prepare to give an interview in a way that objective criteria can be met it takes quite a bit of preparation. Anything other than that is just developers deluding themselves into thinking that they can actually evaluate technical merit in a short interval of time. Moreover any individual might overall provide benefit to a team while in some technical way being less than proficient.
I.explore.code wrote: Is asking such questions even a point here?
My only goal is to get them talking about any technical matter merely to see if it appears that we will be able to communicate in a reasonable way.
|
|
|
|
|
PETA's gonna get this guy black-balled from future Twilight (groan) movies: [^].
«To kill an error's as good a service, sometimes better than, establishing new truth or fact.» Charles Darwin in "Prospero's Precepts"
|
|
|
|
|
Some people have never heard of Peter Sellers, obviously.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Phuket, who cares. 
|
|
|
|
|
Once again, the elephant gets all the girls. Go figure...
Will Rogers never met me.
|
|
|
|
|
Dee swallows choke without emotional involvement [6]
|
|
|
|
|
Good one! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Pretty tough!
What's the solution?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
You have to get up pretty early to fool me! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Hey! You're supposed to be helpful!
CODZ PLZZZ!!!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
public static void Main(string[] args)
{
Console.Writeline("You have to get up pretty early to fool me! :laugh:");
}
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
'System.Console' does not contain a definition for 'Writeline'. 
You have just been Sharapova'd.
|
|
|
|
|
It's an extension method which also writes it to a log file... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
An extension method for a static class/method? 
You have just been Sharapova'd.
|
|
|
|
|
It only looks like C# ... it's a new prototype language called "Visual MakingThisUpAsIGoAlong#++.NET"
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
My boss said it broke his puter an i is fired.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
