I believe that the 'using namespace ;' is discouraged now-a-days.
I believe the more preferred way is to be explicit by 'using std::cout;' for each and every function you want to "shorten/cleanup"
Ask HN: Scolded on a job interview for not namespacing
61–69 of 69 posts
Re: Ask HN: Scolded on a job interview for not namespacing
#62Honestly 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…
Why bother giving feedback to the recruiter? That's only going to improve the company he's not going to be working at, rewarding them for already failing to do their jobs (who put this guy is an interviewer's position? etc.)
I agree with the "don't give them feedback" but for a different reason.
If the company has this psycho in there interview rotation, he sends a strong negative signal, basically the company has a "tell" that candidates can use to avoid this guy or companies that would employ him.
If the recruiter coaches them to hide their "tell" [removed the guy from the interview rotation], they haven't really fixed the problem, just hidden it. Now, the next guy/girl who interviews won't know about the horrible guy he/she will be working with because the company "hid" him from view until it was too late.
Re: Ask HN: Scolded on a job interview for not namespacing
#63Earlier 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.
It will keep candidates from knowing about this bad interviewer - until they are hired. Now you may be stuck working with the guy. I would not tell the company for this reason.
Re: Ask HN: Scolded on a job interview for not namespacing
#64Were you able to complete the problem within reasonable time, otherwise?
As an interviewer, I get frustrated if the candidate wastes time writing excessively prolix text while missing the meat of the question. This is by no means an excuse for hostile conduct, and the additional context here makes it clear the interviewer is kind of a jerk in addition to being narrow-minded.
Re: Ask HN: Scolded on a job interview for not namespacing
#65Ah Quants. All the best shouting matches in my last office were between the Quants arguing over things that ultimately were a matter of taste. Proper storming out and slamming of doors arguments.
Quants are maybe math half-god but the bests I worked with are average programmer. Most of them are awful programmers, and it's not a problem as long as their code is only the prototype for cs engineer to implement in a better way.
Re: Ask HN: Scolded on a job interview for not namespacing
#66Ah Quants. All the best shouting matches in my last office were between the Quants arguing over things that ultimately were a matter of taste. Proper storming out and slamming of doors arguments.
In the short time that I worked at a quantitative hedge fund (all of 2007, basically), the quants were the absolute nicest, friendliest people in the whole company. If you were even slightly technical and curious, almost any of them would answer whatever questions you had and would casually shoot the shit about anything in their nerdy areas of interest. This in contrast with the one floor trader who repeatedly and fo…
I've known lovely quants. Can't think of any traders who were just plain nice.
But their ability to (as frankly average programmers) get into shouting matches (in front of a room full of above average programmers) about shit that didn't matter? Never been beaten.
Re: Ask HN: Scolded on a job interview for not namespacing
#67I don't write C++, but in Haskell I always either list what I'm importing in the import declaration:
import Data.Time.LocalTime (getZonedTime, localDay)
import qualified Data.Aeson as J
> and why would any programmer use functions with the same name
Because they would otherwise be resorting to Hungarian notation.
For example, J.Value in my example above is for JSON values, but if I were to import:
import qualified Database.Esqueleto as E
Similarly, `Data.List.empty` tells me if a list is empty, while `Data.Set.empty` tells me if a set is empty.
Re: Ask HN: Scolded on a job interview for not namespacing
#68As someone who have worked in quant firm when people are losing money they go mad.
Usually, interviewer wanted to put me into high pressure/stress mode to see if i could still function rationally.
Not everyone does, i also saw guys who choked or started bleeding or lost their temper and became violent literally when put under pressure. If the job has such environment - interviewer must test whether you fit in or you'll be better staying out of it for your own good. Cheers!
Re: Ask HN: Scolded on a job interview for not namespacing
#69Lot of pricks in this industry. Tell him to f off.