Man Catches Job Interviewee Cheating During Skype Interview
-
Obviously I know that and you know that....but they got real suspicious if I stopped typing for even a few moments asking if I was ok. Typical interview BS that is more about jumping through hoops than the real world. The test involved using an ArrayList which is something I've literally never used because, well, why would you? It is a non-strongly-typed relic from before the days of generics. After I worked out what the heck it was and how you put things in and got things out I think they were testing how robust the code I was writing was, ie was I using "as" and "is" etc and not just assuming types and casts.
I would have probably started my answer with "Nobody in their right-f*ckin mind uses an
ArrayList." :)".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 -
I would have probably started my answer with "Nobody in their right-f*ckin mind uses an
ArrayList." :)".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 -
I thought the ability to Google stuff was a pretty important quality for a developer, it shouldn't be frowned upon. Well, unless you Google "Send Codez Plz" that is :laugh:
OK - so I googled "Send Codez Plz[^]". Maybe I should have used Bing?
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
Very possibly that was the desired answer.
Yeah, probably, but my "added syntactic sugar" in the form of the word "f*ckin" would probably have lost me the job. Ah well... opportunities missed, and all that. :) THIS! IS! SPARTA!
".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 -
A "live code challenge" should not preclude one from using google. I google pretty much everything before doing any coding. It's not "cheating" - it's "coding". There's simply TOO MUCH to learn nowadays, and there's no way a normal person can learn and retain it all. Expecting that is not only unreasonable, but is absurd as well.
".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, 2013I agree 100%. I've often said that during an interview the interviewer can ask me one question about a technology that is obscure to me and very known to her and I'll look like an idiot. But, just as quickly, I could ask the interviewer about an obscure thing that I know tons about and make the interviewer look like an idiot.
-
I thought the ability to Google stuff was a pretty important quality for a developer, it shouldn't be frowned upon. Well, unless you Google "Send Codez Plz" that is :laugh:
It is very important and it is incredible how many people are search engine-impaired, judging from Q&A that is.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
QA in video form :D Not gonna lie, I had to do a "live coding challenge" as part of a remote interview once and googling syntax in one window while trying to continue typing in the code window to hide the fact that you're google in the background was pretty challenging....I'm sure they were onto me :D
I am so glad to be done with all of that interview nonsense. I am working my last job and when it is done, I am done. I never had to do any kind of 'code challenge'. Anytime a recruiter informed me that the employer required one, I simply refused the interview. There's only some much BS I was willing to put up with. And it's all over now. :thumbsup:
Frank Wilhoit: “Conservatism consists of exactly one proposition …There must be in-groups whom the law protects but does not bind, alongside out-groups whom the law binds but does not protect.” We never have had a president* so completely deserving of scorn and yet so small in the office that it almost seems a waste of time and energy to summon the requisite contempt
-
Man Catches Job Interviewee Cheating During Skype Interview So have you worked on any triggers ! lol...
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
"... and I don't want to catch anyone not cheating during the test."
-
A "live code challenge" should not preclude one from using google. I google pretty much everything before doing any coding. It's not "cheating" - it's "coding". There's simply TOO MUCH to learn nowadays, and there's no way a normal person can learn and retain it all. Expecting that is not only unreasonable, but is absurd as well.
".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 -
It is very important and it is incredible how many people are search engine-impaired, judging from Q&A that is.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
You are correct. I haven't ever asked a programming question here or anywhere else. Well I have asked third party suppliers because I have paid for it. Then usually it is confirmed as a known issue to be fixed in the next release. But every time I have a question I always find an answer or a workaround via a search engine. Then again, often this is because some search engine impaired individual has been slack enough to not do the search properly in the first place and then asks the dumb question, and that is where I get the answer. It all goes around.... It must be embarrassing to ask a question and the response is a list of links which answers it. It just means that you are either lazy or are a search engine impaired person. Both of these are bad but the lazy bit is stupid because you could have got the answer almost instantly instead of waiting days to get a reply that could help you from some kind person. I don't have time to spare. Search engine skills are a necessity.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
-
I am so glad to be done with all of that interview nonsense. I am working my last job and when it is done, I am done. I never had to do any kind of 'code challenge'. Anytime a recruiter informed me that the employer required one, I simply refused the interview. There's only some much BS I was willing to put up with. And it's all over now. :thumbsup:
Frank Wilhoit: “Conservatism consists of exactly one proposition …There must be in-groups whom the law protects but does not bind, alongside out-groups whom the law binds but does not protect.” We never have had a president* so completely deserving of scorn and yet so small in the office that it almost seems a waste of time and energy to summon the requisite contempt
It's a good way for an employer to signal that they're clueless about tech.
-
A "live code challenge" should not preclude one from using google. I google pretty much everything before doing any coding. It's not "cheating" - it's "coding". There's simply TOO MUCH to learn nowadays, and there's no way a normal person can learn and retain it all. Expecting that is not only unreasonable, but is absurd as well.
".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, 2013True dat!
I don't know anymore, I just don't.
-
You are correct. I haven't ever asked a programming question here or anywhere else. Well I have asked third party suppliers because I have paid for it. Then usually it is confirmed as a known issue to be fixed in the next release. But every time I have a question I always find an answer or a workaround via a search engine. Then again, often this is because some search engine impaired individual has been slack enough to not do the search properly in the first place and then asks the dumb question, and that is where I get the answer. It all goes around.... It must be embarrassing to ask a question and the response is a list of links which answers it. It just means that you are either lazy or are a search engine impaired person. Both of these are bad but the lazy bit is stupid because you could have got the answer almost instantly instead of waiting days to get a reply that could help you from some kind person. I don't have time to spare. Search engine skills are a necessity.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
-
QA in video form :D Not gonna lie, I had to do a "live coding challenge" as part of a remote interview once and googling syntax in one window while trying to continue typing in the code window to hide the fact that you're google in the background was pretty challenging....I'm sure they were onto me :D
I have a windows hotkey that selects the current line and opens a new browser window with a duckduckgo search... As long as it opens on the other monitor, I am good! But TBH, I don't care if someone googles the syntax. Geez... I have programmed in over 30 languages. There is Nuance and Syntax all the time... The important skills is the problem solving!
-
You are correct. I haven't ever asked a programming question here or anywhere else. Well I have asked third party suppliers because I have paid for it. Then usually it is confirmed as a known issue to be fixed in the next release. But every time I have a question I always find an answer or a workaround via a search engine. Then again, often this is because some search engine impaired individual has been slack enough to not do the search properly in the first place and then asks the dumb question, and that is where I get the answer. It all goes around.... It must be embarrassing to ask a question and the response is a list of links which answers it. It just means that you are either lazy or are a search engine impaired person. Both of these are bad but the lazy bit is stupid because you could have got the answer almost instantly instead of waiting days to get a reply that could help you from some kind person. I don't have time to spare. Search engine skills are a necessity.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
Sometimes, when faced with a problem the first time, it's hard to describe it in a way that is easy to Google. E.g. I remember that I was trying to find a solution to a problem I was having in SQL, and it took me about an hour until I found that it is a common problem called "Gaps and Islands". Once I knew the name, I got my answer in a couple of minutes. You also have to remember that for most of the people working in IT (70/80%?), English is not their first language.
-
Sometimes, when faced with a problem the first time, it's hard to describe it in a way that is easy to Google. E.g. I remember that I was trying to find a solution to a problem I was having in SQL, and it took me about an hour until I found that it is a common problem called "Gaps and Islands". Once I knew the name, I got my answer in a couple of minutes. You also have to remember that for most of the people working in IT (70/80%?), English is not their first language.
F Margueirat wrote:
You also have to remember that for most of the people working in IT (70/80%?), English is not their first language.
Good point. It has to make everything a bit harder. Many of my most successful searches are just a collection or jumble of words that don't make much sense. Adding one more word can refine the result. But you have to know the words to begin with.
F Margueirat wrote:
and it took me about an hour until I found that it is a common problem
Spending an hour is a bit tedious but it is also quite efficient. Asking the question and waiting 3 to 5 days to find that it is a common problem, or getting the key name, is worse, as it holds up your work. So that one hour was a good investment I think.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
-
-
F Margueirat wrote:
You also have to remember that for most of the people working in IT (70/80%?), English is not their first language.
Good point. It has to make everything a bit harder. Many of my most successful searches are just a collection or jumble of words that don't make much sense. Adding one more word can refine the result. But you have to know the words to begin with.
F Margueirat wrote:
and it took me about an hour until I found that it is a common problem
Spending an hour is a bit tedious but it is also quite efficient. Asking the question and waiting 3 to 5 days to find that it is a common problem, or getting the key name, is worse, as it holds up your work. So that one hour was a good investment I think.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
Spending an hour is a bit tedious but it is also quite efficient. Asking the question and waiting 3 to 5 days to find that it is a common problem, or getting the key name, is worse, as it holds up your work. So that one hour was a good investment I think.
I agree, I rarely ask questions myself, 99% of the times I find the answer from people that asked the same question. But the times I asked the question, I kept googling while waiting for an answer. In any case, calling someone search engine impaired person because they couldn't find the answer is a little harsh don't you think?
-
Man Catches Job Interviewee Cheating During Skype Interview So have you worked on any triggers ! lol...
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
Actually, I've a different take on this whole discussion about search engine impaired-ness. Such code challenge stuff during an interview is nearly always an indication of absolute clueless-ness of the interviewer. Though it tends to mean they've got some search engine skills and probably got those questions from exactly the same spot you're now finding in your search. I.e. it's a situation of: "This guy's coding much to close to the answer we found online. He must be cheating."
