Make sure you tell him its the dumb bubble sort, not the optimized one. That will show them.Rule of thumb .. you hire smart people..
Noodle tell them that your favorite sorting algorithm is bubble-sort, with a straight face.
My favorite sort is quantum computing monkey sort. Theoretically the fastest available sort .... once quantum computing exists ya know.Rule of thumb .. you hire smart people..
Noodle tell them that your favorite sorting algorithm is bubble-sort, with a straight face.
The guy really pissed me off. The job description was for some hard drive engineering position and he was asking strange questions about linux and Windows and topics I didn't understand. I can't remember it very clearly, but he was definitely far away from what the job description said - and I soon found out the listing was wrong. He kept making large audible sighs like he was clearly displeased with me and then said something insulting about my education before asking the awesome linux question.Rofl that has got to be the stupidest question I've ever heard for an interview
Certainly, but what he was asking was retarded. He also got really butt hurt that I had never used windbg, even though I told him we did real time debugging with hardware emulators instead.Knowing how different OSs implement certain file systems is definitely helpful.
How else can you weed out some of the people who, on paper, have skills but in reality have none? Sure occasionally you have shit like this happen:They're just utterly insulting to the candidates and for the most part filter out the best ones. Practices are insane because no one wants to admit the collective intelligence of mankind's best hiring practice is just "try them out", and almost nothing else has data to back it.
Dont get me wrong. I am not arguing for or against the merits of such practices. I am taking what I consider a reasonable stance on the necessity of some sort of screening and feel that problem solving is a good way to approach it.Not to be obtuse but you can't back that statement up with fact(Not trying to be combative, there really is no positive correlations with almost every hiring practice).
The *only* practice I've seen consistently show a positive correlation is the "take home test" variety, where they give you a task, you have an unlimited(within reason)time to complete it, and are allowed to use any tools or methodology you want.
Even that isn't perfect because you can still cheat, though it's easier to tell who is cheating when you actually discuss it with them. The reason it seems effective is because it's the only hiring practice that simulates a real working setup.
Even that though has downsides when interviewing for multiple companies, I had to do 10 of those in the course of two weeks recently, it's very time consuming to the applicant.
Hiring is counter intuitive, and something I spend a lot of time on, people like Jonathon Blow in your link are part of the fucking problem, these snob programmers who pretend even basic algorithims memorization is part of the day to day job.
I think that on average, its better to hire people between "holy shit CS god" and "holy shit have you ever seen a keyboard?" than to strive for the edge cases.But that's the counter intuitive bit, the screening isn't screening for what you want. It will weed out some stinkers, but it also weeds out some of the best candidates. So now you're recruiting from the "meh" pool, on aggregate, you are going to get worse hires than RNG.
How long have you been working in the industry wormie?I think that on average, its better to hire people between "holy shit CS god" and "holy shit have you ever seen a keyboard?" than to strive for the edge cases.
Depends on the culture but generally I think for a developer job a suit is a tad overkill. I just shirt and tie it.We had a holy shit CS (computer engineering) god here that went right to Google after his 2 years here, I would assume most of those guys don't stick around long. I look at some of the work he did in his time here and I can't even compete.
Stupid question - for interviews suit or no suit? I've done both, but I don't know what's preferred.
I dont work in the industry. I have mentioned that fact in this thread before. Frankly I find the day to day development boring as balls and any job that I would want to do in the industry requires having a PHD which I do not yet have. My exposure to software developers is limited to the meetups I attend a month and the sea of undergrad/grad students that surrounds me almost every day.How long have you been working in the industry wormie?