Urban legend, former IMDb editor, conference speaker, Seattle CoderDojo organizer. Love finding inspiration in dev tools and products, then sharing it with dev communities.
Location
Seattle, WA
Education
BA in Creative Writing, self-taught + some certification courses in modern programming languages
May be worth noting that such coding challenges are also a self-reinforcing pattern. The more people the process flunks, the more your people who passed it are likely to consider it valuable.
Three reasons behind that:
The higher the failure rate, the more it makes some feel like those who pass are "the best of the best."
The stronger that feeling, the more current employees may find their success at it feels validating, reinforcing a sense of self-worth.
Like fraternity members who had to go through hazing to get initiated, there can even be a sense of righteous injustice that new members wouldn't have to pass through the same level of Hell to join their ranks.
If you're seriously considering changing your process, that reinforcement and bias may result in serious push-back against the changes.
May be worth noting that such coding challenges are also a self-reinforcing pattern. The more people the process flunks, the more your people who passed it are likely to consider it valuable.
Three reasons behind that:
The higher the failure rate, the more it makes some feel like those who pass are "the best of the best."
The stronger that feeling, the more current employees may find their success at it feels validating, reinforcing a sense of self-worth.
Like fraternity members who had to go through hazing to get initiated, there can even be a sense of righteous injustice that new members wouldn't have to pass through the same level of Hell to join their ranks.
If you're seriously considering changing your process, that reinforcement and bias may result in serious push-back against the changes.
well said
Definitely can see how those biases will keep people from being okay with making these changes.