4 ms·
This is so true. I see a lot of job ads that seem to require very specific experience, but where anyone in that field could do the job. If you just make up eg
by lordnacho 12y ago
This is so true. I see a lot of job ads that seem to require very specific experience, but where anyone in that field could do the job.
If you just make up eg 4 different types of technology, and put a few things in each bracket:
[SVN, Git, Mercurial, CVS]
[MySQL, PostgreSQL, Oracle, MSSQL]
[AMQP, MQTT, STOMP, RabbitMQ]
[Java, C#, C++, ObjC]
Now if someone came along and said they'd solved a domain problem (eg trading systems) with one of each of those, I would more or less believe they could do it with any of the others, with a bit of time to get used to things (particularly c++).
But if you don't believe that, ie if you decide the person must have a specific combination, then you've just shattered the potential pool of applicants into 256 little pieces.
The other thing that annoys me is the pettiness of the interview questions. So many things that you could easily google can be used to stump anyone. What's the default implementation of GetHash() in c#? I actually got asked this once.
Then there's the other way to do things, which is to do an online coding assessment. I guess this gets rid of the FizzBuzz failures, but it tends to be a problem that's too small to see if you're about to dig a hole.
- barrkel 12y agoWhat's the default implementation of GetHash() in c#? I actually like this question (not that I've ever asked it before), because it teases out how well someone knows .net and C#. The specific implementation of GetHashCode isn't what's interesting. It's whether you know that .net implements reference vs value equality by default, whether you know you really do need to override GetHashCode if you override Equals, testing if you know the fundamental requirements for objects you might use as keys in a Dictionary. The specific number returned and its relationship with the identity of the object - that's not important, and is truly not something you could be expected to know. But you're ability to think things through, and know the environment - yes.
- jhall1468 12y agoBull. It teases out if someone happens to know the GetHash() implementation in C#. Their knowledge of .NET and C# can, in no way, be determined by one stupid question about the implementation of a specific function in C#. Evidence of that fact is in your actual response: I could now answer that question, having never used .NET or C#.
- deleted 12y ago[deleted]
- Retric 12y agoI would go so far as to say someone with that kind of encyclopedic understanding of a language is a negative indicator. People with an 'deep' understanding of a language like to use said knowledge to create 'Clever' code. 'Clever' code is generally more buggy, harder to maintain, and basically never needed. PS: And yes, I have been burned by this in the past often enough so I will now pass on a few marginal people that happen to know a language 'deeply'.
- DanielBMarkham 12y agoHere's my exact train of thought while reading that: GetHash? What the frack? Isn't that on object somewhere? Right, object handles all the common copy semantics and so forth. Use the hash to check for equality; things on the stack instead of the heap, yadda yadda.. Dang, here the guy is going into detail why this is so important. Ah yes, value versus reference semantics. Boxing and so forth. Tiny trivia around how the CLR works. I remember those days well. Would make for a great Nerd Jeopardy question. But who cares about all of that? I'll look it up if I need it. As far as memory usage, I worry about that by using pure FP and being careful what kinds of data structures I use. Problem solved. Encyclopedic knowledge is great, but the real trick is dumping everything possible offline and then knowing how and when you should get back to looking at it.
- eropple 12y agoWhile in the general case I would agree with you and I try very hard to dump as much stuff offline as possible, I would argue that this is one of those things you cannot look up "if you need it", similar to the difference between 'class' and 'struct' in C# or the difference between 'class' and 'case class' in Scala (the C# one being a runtime implementation difference, the latter being a fairly large OO design difference). It's something you need to internalize to do well in the language and the environment. C# (and similarly Java) are so tightly coupled to their runtime languages that, personally, I do feel like I need to understand stuff like this at an intuitive, not-even-thinking-about-it level to be able to write good, fast, clean code.
- mordae 12y agoSenior programmer would know that he needs to check hashing mechanism when his custom dictionary keys were not working right. Everything eventually boils down to the bunch of algorithms Knuth so carefully documented for us. Learning a new language is just learning the syntax and semantics for it's mapping to those algorithms. Stop holding languages in so high regard, jeez. IT is held back by this so much it hurts. Let's just describe some sensible high-level evaluation semantics and start all compiling into that already!
- graycat 12y agoNever heard of GetHash. I've got 5000+ Web pages of documentation mostly just on the .NET Framework, am betting my start up on .NET, ASP.NET, ADO.NET, and Visual Basic .NET, and have yet to encounter GetHash. From the mnemonics of the naming, a guess is that GetHash has to do with hashing. Well, mostly I don't like hashing and prefer extendible hashing, AVL trees, red-black trees, B-trees, heaps, etc. Typically, for a class in the .NET Framework, to use it for the first time have to find a dozen or so Web pages at MSDN and learn them: For me that means download, index, abstract, and read the pages, look at the sample code, and maybe write some minimal code to exercise the class. Yes, being clear on call by reference versus call by value is important but also quite elementary. Basically, all aggregates are to be call by reference; simple numeric constancts are commonly call by value.
- atonse 12y agoI've been writing apps in C# for about 5 years, and not once have I needed to know how GetHashCode works. I have looked at it at some point (don't remember why, I think it had to do with an entity's identity for NHibernate) but I would fail this question even though most people I've worked with would rate me as a very effective (and efficient) programmer. This is why I feel I would do badly in these kinds of trivia-like interviews (once since I put linux administration on my resume, I was asked how to delimit lines in bash scripting). My dream interview, one where I'd shine, is where I'm given a problem, and I have to go through designing solutions and discussing tradeoffs. I don't mind writing code either, but I would not know the answer to this kind of very specific question, I'd just know how to solve problems.
- barrkel 12y agoHave you never written a class that you wanted to use as a key in a dictionary? You need to know the contract of GetHashCode to do this properly. If you don't know the contract of GetHashCode, well, you simply don't know .NET very well. That's my professional opinion.
- scintill76 12y agoI don't know much C#, but can't one understand the contract without knowing the default implementation? I would agree understanding the contract is probably essential, but the implementation is not.
- ajross 12y agoHere's the thing though: the reason people hiring get so hung up on specifics is because they get burned repeatedly. Coding is just hard. Learning it is hard, doing it is hard, and there aren't enough people who can do it well to go around. So if you're a manager and need to "build a team", you can either play that needle in the haystack game (which you will always lose, because the needles generally don't even show up on your list of resumes) or you can try to cheat: find someone who has done exactly what you are doing in the past. Obviously that doesn't work either, but it's not irrational to believe it might.
- S4M 12y agoDo you think someone who is familiar with git wouldn't be able to be productive with svn in more than one day (while doing other tasks of course)? Getting familiar with the code base takes much longer than picking up C# if you have a Java background.
- ajross 12y agoWhy are you arguing with me? I agree with you, and said so. I was trying to explain the thought processes of those who don't. Basically, managers get burned repeatedly trying to hire people who aren't productive. And the reasons they aren't productive ultimately do end up being "So and so has been here for six months and still doesn't know subversion [or C#, or whatever]". So... the logic goes that if you hired for that skill in the first place you wouldn't have this problem.
- prostoalex 12y agoA lot of programming nowadays is not as much about writing primitives, but knowing ins and outs of specific frameworks and libraries. How reasonable would it be to expect an Objective C / Swift guy to write high-quality C++ Boost code and vice versa? In every company there's some amount of code that's written in X but definitely looks like the person writing it was more experienced in Y and just dragged Y idioms into his new project.
- jethro_tell 12y agoYes, this is true, but also misses the point. You might be looking for a C++ programmer, but because of the way the add is written, your HR is going to skip over the guy who didn't write git on his resume.
- V-2 12y agoThere are different paradigms even within one and the same language. Eg. Android apps written by Enterprise Java guys are just awful.
- anon4 12y agoIf they are a really good programmer, they most probably have touched pretty much every popular language and paradigm. Give them one to two weeks to get used to the language and another couple of weeks to get used to the frameworks.