4 ms·
> 1) Are there really people who claim SQL Server 'expertise' and then not know things like the difference between DELETE and TRUNCATE? Yes, but this isn't spe
by dspillett 15y ago
> 1) Are there really people who claim SQL Server 'expertise' and then not know things like the difference between DELETE and TRUNCATE?
Yes, but this isn't specifically a SQL Server thing. People will often inflate their skills ridiculously on their CV, sometimes just telling bare faced lies. I once had to deal with an idiot who despite his CV listing him as knowing Javascript to an "advanced" level and jQuery specifically at an "intermediate" level, did not understand what $(<function>); did and was no wiser when we took out all the shortcuts to produce jQuery(document).ready(<function>); I wish I was jesting or exaggerating here. You should have seen the vacant look on his face when we tried to explain a very simple closure. Advanced indeed...
> 2) If above is true, then am I short-selling myself by not putting SQL Server in my resume?!
Possibly. If you understand all the basics covered in that document and have actually used them (rather than just having read about them) then yes. But be very careful to stay aware that knowledge does not necessarily imply experience (nor vice versa) - chose your wording carefully to put yourself in the best light you can without bending the truth (or seeming like you are trying to) implausibly.
Claiming expertise is another step forward: if you say you are an expert that sets the level of expectation very high - you will be expected to have an excellent level of both practical and theoretical knowledge (the how and the why) and a lot of experience to back this up. If you ever claim to be an expert be quite explicit what you are an expert in. If your expertise is in the DBA side of things or from a programmers perspective (to give two generic examples) say so - databases cover a large area of subject matter and you can command a high price if you are truly an expert in the lot!
Basically out on your CV the level that you would be comfortable being asked questions about. If you have some experience or knowledge of SQL Server then by all means say so but try not to exaggerate. If you have experience with SQL based RDBMSs other than SQL server then put that instead (as the basics and some of the not-so-basics are very much transferable) but don't claim SQL Server specific experience unless that is what you actually have.
- dpcx 15y ago> You should have seen the vacant look on his face when we tried to explain a very simple closure. Advanced indeed... Being able to describe a closure is only valid if you've had reason to use them before. Sure, use of jQuery pretty much implies use of closures, but in general, lack of specific knowledge within a domain does not imply lack of knowledge in the domain.
- jeltz 15y agoI would say any real use of JavaScript does imply use of closures. For example most frameworks and any use of AJAX requires them to be used.
- dspillett 15y agoA fair point: you can get by without them completely for many tasks, or with them but not actually knowing you are using them (and/or what to call them) because you've not needed to understand the implications in detail (i.e. you might pass out an inner function and merrily call it, or hand a function that uses state outside its internal scope to some library, without knowing that these are closures). But to not be able to grasp it at all when explained (he wasn't being asked to describe them from his own understanding), definitely marks "javascript: advanced" as an exaggeration far too far IMO. To be honest I wasn't being really fair with the closure thing. I should have not proceeded as we'd already left his safety zone long before that point. Anonymous functions were alien to him, and I'm not sure he was even comfortable with the idea of functions being entities that you could pass around at all (i.e. do anything with other than define and call). To put is simply: I considered his level of knowledge/experience to be no better than basic, perhaps not even that, unless you count having copied and pasted some more advanced code samples, and his CV claimed "advanced". And not recognising jQuery(document).ready() or any of its shorter equivalents made his level of anything with jQuery "none" rather than "intermediate" claimed (making that an flat out lie instead of just a gross exaggeration).