737
Dev Interviews (lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
[-] danc4498@lemmy.world 6 points 1 week ago

Maybe it’s about being able to communicate an algorithm verbally. Unless these are written interviews, then yeah, probably pointless.

Also, I do think being able to understand how an algorithm works is probably important on its own.

[-] qarbone@lemmy.world 9 points 1 week ago

Then give them some code and tell them to explain it. Having testees regurgitate algorithm implementations from memory is just testing rote memory.

I thought we had all lived through terrible public schools that just tested memory, and resolved to do better.

[-] BombOmOm@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

Yeah, it's a solved problem. I'm going to call the library's default sort and move on. If it somehow is a problem, I'll revisit later.

Now, optimizing database calls, fixing (and avoiding!) security holes, writing tests that don't take forever to run, writing functions so they can be easily re-used later, and not duplicating code. Now there are some skills!

"It's faster if we make a duplicate of this function and change this section, then we can move onto other things"

"No it's much slower, because your code review just came back telling you to throw that idea in the garbage and do it right"

[-] frezik@midwest.social 1 points 1 week ago

There's a lot of ways to test communication skills. This doesn't seem like a very good one.

this post was submitted on 08 Apr 2025
737 points (98.4% liked)

Programmer Humor

22506 readers
1098 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS