News for hackers. Stuff that matters.
Re:AI Killed the Tech Interview. Now What? by bdavisx on Thursday February 20, 2025 @07:58AM (#43114130)
Here's an interesting thought on your "gotcha" - I'm 57 years old, been programming as a career for over 30 years, a lot of languages and I have no idea what the difference is.
Re:AI Killed the Tech Interview. Now What? by dennis_jeeves2 on Thursday February 20, 2025 @08:13AM (#43114238)
I have no idea either. I can easily look it up though. You can often tell an inexperienced interviewer from the extremely domain specific question they ask which _they_ are familiar with.
Re:AI Killed the Tech Interview. Now What? by Clubber on Thursday February 20, 2025 @08:15AM (#43114252)
>You can often tell an inexperienced interviewer from the extremely domain specific question they ask which _they_ are familiar with.

Lol a bit touchy aren't we?

Like I said, it's not really relevant in today's languages. It was for a Delphi/Pascal position. If you do any type of database code (like T-SQL), you would also know it. If your experience is mainly in C type languages, everything is a function so it doesn't apply.

Re:AI Killed the Tech Interview. Now What? by dennis_jeeves2 on Thursday February 20, 2025 @08:39AM (#43114488)
I think you are missing my point.

Words like functions/procedures tend to have different connotations across languages and once one crosses one's 15th language, and each having some 20 different keywords, it become difficult to remember what the exact connotation of a word is, in a specific language/framework. This is the most likely situation of the guy whose post I responded to.

The exception to the rule is, if you have been working quite a bit _recently_ on a specific language. You are presumably talking about this situation.

Re:AI Killed the Tech Interview. Now What? by dennis_jeeves2 on Thursday February 20, 2025 @09:01AM (#43114721)
>Lol a bit touchy aren't we?

No. I just looked up other responses to your post. It's obvious you got exposed as being inexperienced (or an idiot), while posing to know the definitive with your "gotcha". Being inexperienced (or ignorant) is not a problem, but being cocky is.

Re:AI Killed the Tech Interview. Now What? by Clubber on Thursday February 20, 2025 @10:49AM (#43116138)
I think you're projecting. You aren't posting this using your real name are you?!
Re:AI Killed the Tech Interview. Now What? by dennis_jeeves2 on Thursday February 20, 2025 @06:05PM (#43121645)
Look up my other responses - I decided to call you names _later_ . Other people also pointed that out to you. I'm sure you would thick twice before asking your 'gotcha' again (the question is fine in general but not as a gotcha).
Re:AI Killed the Tech Interview. Now What? by Clubber on Thursday February 20, 2025 @06:28PM (#43121887)
>>You can often tell an inexperienced interviewer from the extremely domain specific question they ask which _they_ are familiar with.

>Lol a bit touchy aren't we?

You lost your composure and decided to start calling names after this. I haven't asked it since the late 90s, early 2000s. It was a for a Delphi position. It's a bonehead easy question any Delphi developer who got to chapter 2 of any Delphi book would have understood. It's still an applicable question for a SQL developer and it's just as easy. I even showed you sample code. I don't see why you aren't getting it.

Re:AI Killed the Tech Interview. Now What? by dennis_jeeves2 on Thursday February 20, 2025 @06:58PM (#43122229)
I'm not getting it, I also see that 2 other people are also not getting it.

>I haven't asked it since the late 90s, early 2000s.

You overall gave the impression that you are currently asking it.

And a personal rhetorical question - aren't you too old to even state this 'gotcha' business _today_ about what you did in the past? What made you state it? If I gave you the benefit of doubt - that was slip, where you omitted the past tense.

(If I did that in the 90's I'd be a embarrassed to even mention it today.)

Re:AI Killed the Tech Interview. Now What? by Clubber on Thursday February 20, 2025 @07:30PM (#43122542)
>I'm not getting it, I also see that 2 other people are also not getting it.

Yes, but you're the only one who threw a tantrum. Enjoy your career.

Re:AI Killed the Tech Interview. Now What? by alexjplant on Thursday February 20, 2025 @11:00AM (#43116276)
> Our "gotcha," which doesn't apply to most languages anymore is, "What's the difference between a function and a procedure." It's a one sentence answer, but people who didn't know it would give some pretty enlightening answers.

If you're asking this question (by virtue of the present-tense "is") in the year 2025 even though by your own admission

> it's not really relevant in today's languages.

then you aren't giving candidates a good impression. Even though I would have nailed this question I would have serious reservations about any job that would ask it in an interview because it means that the person interviewing me has more concern for legacy minutiae than broad technical knowledge or problem-solving skills.

Re:AI Killed the Tech Interview. Now What? by Clubber on Thursday February 20, 2025 @11:30AM (#43116740)
Ya sorry, this was way back in the late 90s-early 00s. It's still only relevant in SQL dev.
Re:AI Killed the Tech Interview. Now What? by ctkhn on Thursday February 20, 2025 @10:15AM (#43115692)
There are some absolutely ridiculous qs I've been asked like this and they've all had no followup question to illuminate why it would have been relevant 1. what version of java do you use? we used 8 at the time 2. what is the engine and version underneath your sql db?this was not for a dba role, just standard backend engineer 3. why did you use python instead of r for x project? this was about a gui automation script
Re:AI Killed the Tech Interview. Now What? by Clubber on Thursday February 20, 2025 @08:13AM (#43114233)
Re:AI Killed the Tech Interview. Now What? by aleph_minus_one on Thursday February 20, 2025 @09:57AM (#43115446)
> A function returns a value

... in Pascal/Delphi.

Re:AI Killed the Tech Interview. Now What? by Clubber on Thursday February 20, 2025 @10:50AM (#43116155)
Yup, it was for a Delphi job in 1998.
Re:AI Killed the Tech Interview. Now What? by vips7L on Thursday February 20, 2025 @05:33PM (#43121221)
Isn't this something the compiler is going to enforce anyway? Why does it matter? If that's the only difference it's kind of inconsequential isn't it?
Re:AI Killed the Tech Interview. Now What? by Clubber on Thursday February 20, 2025 @06:32PM (#43121932)
It's a question to filter out people who don't know a lick of Delphi for a position where the person was coding Delphi. It's like level 2 after the hello world chapter. It's easier than asking a database developer the difference between a query and a view. It's a bonehead simple question that 70% of applicants couldn't answer.

You would be surprised how many bad applicants interviewers get. It's only gotten worse over the last 20 years.

Re:AI Killed the Tech Interview. Now What? by ttyprintk on Thursday February 20, 2025 @08:48AM (#43114587)
It’s ok to say that it’s never professionally mattered. No one has ever been paid to know that. “Are side effects a bad pattern?” Lotsa people have needed to know that on day one.
Re:AI Killed the Tech Interview. Now What? by michaelt on Thursday February 20, 2025 @12:34PM (#43117681)
If I'm applying for a Java position and I claim to have Java experience on my resume, it's perfectly valid for them to ask me the difference between an int, an Integer, and a BigInteger.

But it's certainly not a universal question applicable to all programming languages.

Likewise, Clubber says in their post that their 'gotcha' question doesn't apply to most languages.