Re:The Problems with Live Coding Interviews
by throwaway675309 on Tuesday April 25, 2023 @05:51PM
(#35707194)
I think we're going to see a pretty large industry shift away from take-home tests given how easily 90% of these tests can be gamed using chat GPT.
[ Parent
| on HN ]
Re:The Problems with Live Coding Interviews
by ravenstine on Tuesday April 25, 2023 @06:13PM
(#35707441)
I'd think we'd have already seen this with GitHub Copilot. There was an interview I was part of late last year where the candidate had Copilot turned on during the live coding, and he didn't turn it off even after it was obvious that's what he was using. What I was more surprised by is how I thought this was a bigger deal than everyone else. Like, why come up with these elaborate tests when the candidate is just going to use autocomplete the whole time?
Maybe programming in another few years will just be glorified autocomplete and little more.
And perhaps testing people on how to write code was a mistake to begin with. It's one thing to write code, but reading code is another.
If they are effective at using it to solve problems, why not?
The real challenge is to your testing mechanism and not the candidate
Re:The Problems with Live Coding Interviews
by d0mine on Wednesday April 26, 2023 @07:51AM
(#35712223)
> Maybe programming in another few years will just be glorified autocomplete and little more.
It won't. For the same reason code generation from UML diagrams hasn't replaced programmers [1]. Or why business owner/analysts don't write acceptance tests in Gherkin (Given-When-Then).
Though some tasks that programmers had to do manually in the past may be automated (not the first time).