- I had to Google it...
- According to a StackOverflow answer...
- Person X told me about this nice trick...
- etc.
Stating your sources should surely not be a bad thing, no?
- I had to Google it...
- According to a StackOverflow answer...
- Person X told me about this nice trick...
- etc.
Stating your sources should surely not be a bad thing, no?
But, sadly, OP is right.
When doing a technical screen I'll sometimes pick a skill the person claims to have, and ask them the simplest possible non-trivial question I can ask.
For example, let's say you list 'SQL' as one of the skills on your CV. I might show you a SQL statement like:
SELECT id, start_date FROM employees;
(EDIT: I meant SELECT id, start_date FROM employees ORDER BY id;)I'll tell you id is an auto-increment field, and ask whether the result would show the newest employee at the top or the bottom.
You have a 50/50 chance of getting it right. If you get it wrong, I'll tell you the answer. Getting it wrong wouldn't disqualify you.
Then I'll ask you how to get it in the opposite order.
I am expecting you to immediately say 'add DESC'. If you can't answer that question in under 2 seconds, you probably haven't written enough SQL to justify listing it as a skill on your CV.
You would be surprised at how many people fail simple tests just like this one.
(I won't use this particular one again.)
What is the right answer? Doesn't it depend on the DB? Postgres at least shows rows ordered by last updated time (simplified, I know).
I would be fine if it was "... near the top or bottom" though.
(Or maybe this comment is the correct answer?)
I've gotten so tired of having this argument. Inevitably some clerk will insist on calling me by my first name, "you know, your legal name". No. My middle name is my legal name. It's what my mom, sisters, wife, friends, teachers, coworkers, doctors, and everyone else call me. My first name is an aka at best, except the only people who insist on using it are ones wrong about the law, so I'm not even really "known as" it.
I once closed a bank account 10 minutes after opening it because they insisted that my debit card be printed as "Joe Smith", not "Frank Smith". I told them I'd absolutely refuse to touch it because that's not my name. I find it interesting that it's mostly local orgs who are a pain in the neck about being wrong about this. You'd think a small local bank would know local law better than a huge multi-national, but the giant bank I opened a business account with was totally fine putting Frank Smith on my accounts. Go figure.
(Somewhat related: That's made me super sympathetic to trans people who want to be known as something other than what's written on their birth certificate. Yeah, I get it. It's nails on a chalkboard when someone calls me Joe, so if you don't want people calling you Tammy anymore, I'm on your side.)
Not all systems use that piece of information, but most do.
Having data on every single thing someone does would be handy for all future crimes. Why don't we push for that level of surveillance. Because we are trying to balance with privacy.
Anecdote: coming from a country where this is mandatory, visiting a country where it's not, I almost got run over because I assumed a car was parked when I glanced left before crossing the road.
Of course, might not prove that one or the other is safer, but it did show me how often I subconsciously use headlights as an indicator of off (=> stationary => safe) vs. on (=> potentially moving => potentially a "threat")
I'd say all speakers of all languages have figured it out and your statement is quite confusing, at least to me.