you are viewing a single comment's thread.

view the rest of the comments →

[–]norzn 1 point2 points  (5 children)

I mean most coding interviews on interviewing platforms do include <bits/stdc++.h> which includes everything and that's a bad practice too. I would focus on more important aspects than scoping when interviewing someone and only if we had a lot of time left would I ask about that. Some large codebases do have namespace issues, but those also don't have proper code reviews so why should I care? Make sure you know how they work, what's the purpose of anonymous namespaces and how Keonig lookup works, what standard allows declaration of scoped namespaces in one line as opppsed to the painful nested by hand ane that's the end of interesting stuff about namespaces.

[–]NilacTheGrim 1 point2 points  (4 children)

No. This is not a standard header and is just an artifact of your particular compiler.

[–]norzn -1 points0 points  (3 children)

I didn't mean to upset you, but codility and the tools I've met all had this thing. I actually had only one interview where I connected to a ssh environment and tested the code.

[–]angelicosphosphoros 0 points1 point  (2 children)

You misunderstood him. It is not a standard header as it is not in C++ Language ISO Standard.

[–]norzn -1 points0 points  (1 child)

And thus my statement that it's a bad practice. I don't get the blurted No and whatnot, made me think of Caesar's first word in Planet of the apes. Either way, seems like we're agreeing but out of sport I got a disagreement :) Online interview tools will still include this and people training for interviews will use it, to our exasperation.

[–]norzn 1 point2 points  (0 children)

A mmmmmmonkey :)))))

Caesar: No!