this post was submitted on 07 Oct 2026
-23 points (23.3% liked)
Programming
28764 readers
452 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
yeah, i get that concern.
i don't think the point should be “can this person produce code fastest with an llm.” that would be pretty bleak.
for me the interesting part is almost the opposite: can they still make good engineering decisions with AI in the loop? understand tradeoffs, reject bad suggestions, preserve the design, know when the generated fix is technically valid but wrong for the codebase.
if the assessment only rewards output, then yeah, it just turns people into cogs.
Yeah, you want to hire them. Take the time to learn about them. This reduces the dimensionality of any given candidate to 1.
isn't that only true if you treat the result as the entire interview?
i'm thinking of it more as a way to create evidence for the conversation. not “you passed 8/10 checks so you're good,” but show me how you approached something you hadn't seen before and let's talk through the decisions you made.
I’m going to request we part ways on this one.