this post was submitted on 02 Aug 2025
233 points (96.8% liked)

Programming

21948 readers
755 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Cratermaker@discuss.tchncs.de 15 points 1 day ago* (last edited 1 day ago) (5 children)

I can see how this could be unfair, but working as a dev sometimes does require you to be on top of things in a high stress atmosphere. For example, what if you're proposing an excellent technical solution in a meeting but some jaded older engineer is hard to convince? If you can't outline your thinking in that scenario, your solution could be discarded just because someone was louder than you. As someone who used to have performance anxiety, I believe it's generally something you can and should practice for. On the other hand, if there really isn't a need for this type of skill, it totally makes sense to avoid creating interview environments where you are filtering candidates based on it.

[–] silasmariner@programming.dev 3 points 1 day ago (2 children)

Good enough example, although I would've picked dealing with a live incident

[–] BrianTheeBiscuiteer@lemmy.world 1 points 23 hours ago

That sounds fair. I hate "tests" that involve things you'd never do on the job.

load more comments (1 replies)
load more comments (3 replies)