|
Manhole covers are round because a^2 + b^2 = c^2. Really.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
I was asked something like "How many people are there flying in planes right now?"
I answered "325,761"
The interviewer was stumped!
PooperPig - Coming Soon
|
|
|
|
|
|
Cool. Looks addictive. Must stay away. 
|
|
|
|
|
Yeah, get some work done. For once. 
I mean, with a name like Slacker007...
|
|
|
|
|
Downloaded by five million people who would no doubt look at the Sega Master System or Nintendo NES and sneer, no doubt.
With the exception of Physics games (where the processing power wasn't available), there isn't a game that's played, nowadays, that isn't a variant of games from 8-bit systems; and some of them even look like they come from an 8-bit system (QED) (Yes, I noticed that the physics is slightly better).
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
is just one opportunity![^].
Cheers! 
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
Couple of days ago we had a candidate over for a "Junior Developer" role and a couple of my colleagues interviewed him. After an hour and a half they got back and proclaimed that the guy was no good because he couldn't solve a string reversal problem. Now, that's not the only thing that caused his "demise" obviously it was more of other things like not being passionate about software development in general, not having done a job long enough, not having any side projects to speak and appearing to not even try to solve the problem given during the interview.
What I find funny is these interviewer colleagues of mine really didn't do any preparation or due diligence to interview the candidate, 10 minutes before the interview they were scrambling on websites trawling for questions they can ask. Now that in my opinion is the failure of the interviewer just as much as that of the candidate to prepare properly. I have been to better interviews than this, where the interview lasts for around as much and longer if needed and they assess a lot of soft skills like communication, attitude etc and then some technical grilling on a whiteboard. The process is more two way than this case, the focus is not on solving a problem that you would never actually need to solve from scratch in real life anyway. Why do you think Google was invented? (not talking about "copy-n-pastable" solutions, just general searching for ideas etc.)
What is your opinion on this? Do you think asking "beaten to death" programming questions in an interview is just a lazy interviewing attitude because the interviewer couldn't be bothered to prepare properly? Is asking such questions even a point here?
|
|
|
|
|
It's not about "has it been done before" or even "can he use Google" - it's a way of finding out how he thinks. Does he approach the task in a structured manner? Does he think first, ask sensible questions, or dive straight into code?
Can he even do a simple task without the internet and VS to help him?
Yes - it's an interviewer fail. Yes it's an interviewee fail as well.
Interviews are hard work for the interviewer: like any presentation they take 5 or more times longer to prepare for than to deliver, and if you rush your prep you will not get what you want: a good candidate. A bad interview can put the potential employee off the company, just as much as it puts a company off the potential employee.
Remind your colleagues that interviewing is very expensive: it takes considerable time to weed out the CV's you are interested it, interview candidates, and if you get the wrong one you are both stuck with them for a while and have to repeat the whole process.
"Beaten to death" questions have a place - because any task to be completed within the timeframe of an interview has to be relatively simple or it wastes too much interviewer and interviewee time. But they should be thought out well in advance.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I use programming questions, but I do have certain ones that I bring out time and time again. It's not a laziness thing if it's being done for the right reason. The first thing is, we work in a fairly specific domain so it's an opportunity for me to assess whether or not people can actually answer questions about things that matter to us. Secondly, I'm not bothered about the candidate whiteboarding a solution or typing it in, I want them to engage with me so that they get a chance to find out the types of things we need - the interview is as much about whether they want to work for us as it is the other way around. I'm also not bothered about someone having a confidence issue talking to me in the interview - what I want is for them to give me some part that we can open a dialogue about; the classic case for me is if they say they use TDD, I would be looking to see how this plays into their answers. We can discus issues such as testing asynchronous code, for instance.
TL;DR - they can be useful, but you shouldn't be looking for textbook answers. It's about a dialogue.
|
|
|
|
|
If someone asked me to reverse a string, I'd rotate the paper/monitor.
If they ask me something about the technology they use, I'll think about taking them seriously.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
My only experience is as interviewee, and I've been interviewed only once - when I've been hired in my current company.
The first step was a written questionary with 30 questions to be done in 40 minutes - the questions spaced from generic Computer Science (i.e. calculating a xor between 2 decimal numbers, ginving the result in binary and checking if the given hexadecimal representation of the result was correct), Calculus, Electronics, Signal Theory, C/C++ programming and VB6 (the last 2 were the actual requirements of the job).
After that they called me back some day later for the real interview where we only spoke about my past / side projects, ambitions, inclinations and the company business - what and how they do for living. They were impressed by the sincerity in my curriculum, I checked VB6 as good knowledge and got all the related questions right, while I marked most of the skills as academical, meaning I studied them and passed exams but had not any real experience.
Geek code v 3.12
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*
Weapons extension: ma- k++ F+2 X
I use 1TBS
|
|
|
|
|
The thing to bear in mind with this "stock questions" approach is that the candidate's agent will ask the candidate what question they were asked and use that to prep the next candidate through the door.
|
|
|
|
|
I.explore.code wrote: After an hour and a half
If you can't tell within 10 minutes whether a developer knows what they're talking about or not, you've got problems.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I know one guy who specializes in 4 or 6 hour interviews.
One interviewee asked for a comfort break after three hours, then called reception from his car to tell them to elephant off.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
what do you do for 6 hours, rewrite his website?
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
Hang yourself after about ten minutes, I think...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: I know one guy who specializes in 4 or 6 hour interviews.
Sounds like a guy trying to avoid doing his actual job. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Managing Director, and a total control freak. Still pays employees by cheque (as far as a I know) because that way he can decide if he likes them enough to actually pay them that month.
He did / does that with everyone: from the-pack-and-dispatch guy to the sales manager. I managed to avoid it by giving him no choice but to hire me ... and then create a department for me to "be in" afterwards! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: I know one guy who specializes in 4 or 6 hour interviews.
Is he arrogant, ignorant or both?
|
|
|
|
|
Worse: he spent a year working for Metal Box[^] as an "engineer" before accepting a position in the family firm, and rising rapidly - a promotion a week - so he knows everything technical.
In his mind, anyway.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I had an interview lasted 2 hours, then on the way out was asked to do one of those Psychotic tests, or whatever they're called.
I was about to refuse (they told me it would take between 30 mins and an hour) but they said no test, no job, so I thought waht the heck!
As it was gone 5pm they then buggered off, leaving me in the room to do the test & told me to put the paper on reception on my way out (there was a button to unlock the door) so I was left in this little room behind reception, alone in the building, to do a Psych test!
Fortunately for me, I was totally pissed off at this point, so I ran through the multiple choice questions (they were questions like:
You are at a party when someone spills a drink down your new suit; how do you react?
a) Punch them in the face
b) Apologise to them
c) such the drink out of the cloth
d) Laugh
Stupid bloody questions, this type - I mean, who was it? was it deliberate? am I drunk? was it a cheap suit? had he just shagged my wife in the toilets? Move information needed.
So. I answered them entirely randomly on the answer sheet, finished in all fo three minutes, hung around to make sure the interviewer had time to get out the car park, and buggered off.
The agent phoned me a few days later (they sent the tests out to a company that rips people off about this sort of thing) and told me I had got the best results they'd ever had!
Got the job.
It was crap (they used vi to edit Cobol, in the mid-1990's!)
PooperPig - Coming Soon
|
|
|
|
|
I know, but what's worse is that they spent all that time and still couldn't ask a worthy technical question or may be the candidate just took too long to allow them to move on from the lowest of the low questions to more sensible stuff. I still have little to no respect for these stock questions, just because the candidate says Computer Science on their profile doesn't give you a license to ask these ridiculous questions, unless the candidate doesn't have any commercial experience. IMO these ridiculous "technical" questions should be a last ditch resort after the candidate has failed to show enthusiasm, soft skills, side projects.
|
|
|
|
|
I.explore.code wrote: I still have little to no respect for these stock questions
I agree. I've found the best way to interview anyone is to let them tell me what they've done. It's very clear that way if they know what they're doing.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
For my last two positions, they were phone interviews. The first was for a position working with FORTRAN and FMS (forms application) on VAX/VMS. I knew the platform and supporting tools, but I was also personable enough to be able to talk to the interviewers and present myself as a good candidate.
The interview lasted 2 hours.
The next position (current one) was for a niche market product that I had used for 20 years. Again, I knew the product and I could hold my own technically and personally. That interview lasted an hour.
For people I've interviewed, I've learned to listen for key phrases: if everything is "we've done this" or "our group did that", the person isn't presenting themselves or their work - they are representing what was done by others.
Whether someone can solve a particular problem as a junior should not be as important as do they understand concepts, are they willing to learn, are they willing to be mentored.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
