41–50 of 69 posts
I had an interview where the interviewer was much more concerned about looking smart and presenting his cleverly chosen question, than ever wanting to know if I was a good candidate. I even told him that his overbearing interjections we’re throwing off my rhythm. I never heard back from him. Probably for the better.
Honestly if I ever had someone yell at me in an interview I'd just pick my stuff up and walk out. Cheap way of figuring out you don't want to work there. Give feedback to the recruiter of what is unacceptable behaviour. As to the actual point I'm with you: be explicit. I write std::cout too. Not that I'd get upset if someone used "using namesace std" as long as such using statements are used judiciously, it's fine. L…
I'm with you. I'd say "Thanks for your time" and leave, giving feedback to the recruiter. If anyone at my company did that in an interview, we'd certainly never put them in an interview rotation again, and there might be further repercussions. There's one guy in our office who is a brilliant programmer, but when reviewing code, he's incapable of seeing anything but the negatives. (Upon reflection, he perhaps did this…
isn't is the purpose of code review
More broadly, 'using namespace' is strongly discouraged except for our own namespaces. In all but a very narrow set of exceptions, we prefer to make it immediately obvious what functions are from external dependencies when scanning the code.
If the interviewer finds adding explicit namespaces 'confusing', the problem is with him, not you.
I had a similar experience but, in a much friendly environment except I did the exact opposite. I actually wrote a blog post (https://marcell.me/using-namespace-std/) about this last week, feel free to check it out
I had an interview where the interviewer was much more concerned about looking smart and presenting his cleverly chosen question, than ever wanting to know if I was a good candidate. I even told him that his overbearing interjections we’re throwing off my rhythm. I never heard back from him. Probably for the better.
I’d say that’s 60-80% of interviews. Especially group interviews. Everyone’s first priority is to look smart.
https://medium.com/conquering-corporate-america/10-tricks-to...
I hate typing the same thing over and over... so, yeah, I'd use namespace std. However, for an interview, you are correct. This is something too trivial to mention or "get mad" at...
Taking shortcuts just because you don't like typing a few extra characters is a bad habit to have, it leads to the kinds of code that has obfuscated variable names, no comments, 'clever tricks' that put way too much logic in a single line, etc.
I used to think like you, but I realized saving a few keystrokes is almost never worth it.
Earlier quoted context omitted.
I'm with you. I'd say "Thanks for your time" and leave, giving feedback to the recruiter. If anyone at my company did that in an interview, we'd certainly never put them in an interview rotation again, and there might be further repercussions. There's one guy in our office who is a brilliant programmer, but when reviewing code, he's incapable of seeing anything but the negatives. (Upon reflection, he perhaps did this…
"when reviewing code, he's incapable of seeing anything but the negatives" isn't is the purpose of code review
Earlier quoted context omitted.
> HR department you should consider telling them what happened. Why? Better you dodge a bullet and GTFO. Don't waste time with telling them what they probably already know.
Fine to dodge the bullet, but please always provide the feedback if possible. It takes minimal effort, and can help avoid the same unpleasant experience happening to others in the future.
And that unpleasant experience is also a very good sign to prospective employees to "DONT WORK HERE". If that's how they treat people they're courting, I want to know that up front, rather than see it a month later after relocating. So no, I don't want them to fix it (in reality; delay it).
I want interviews to be the same way as a Unix process: fail quickly and fail loudly. And this interview certainly did that.
(Glowforge, I didn't have the experience in the areas they were asking. And I'm happy they told me. And they were up front with me within 2 days, at that!)
The nearest I've had is a manager who was angry in a 1:1 when I disagreed and blew a gasket. That just made me smile as I thought it was funny but I stopped him there and left the room. Nothing more was ever said of that meeting.