←back to thread

Please stop the coding challenges

(blackentropy.bearblog.dev)
261 points CrazyEmi | 1 comments | | HN request time: 0.485s | source
Show context
simonw ◴[] No.42148072[source]
> This is like asking a Ruby developer to debug PHP as a test of flexibility.

Sounds like an OK test to me. Great (senior) developers should be able to do that kind of thing. Categorizing yourself exclusively as "a Ruby developer" is a career trap.

replies(7): >>42148129 #>>42148133 #>>42148141 #>>42148181 #>>42148243 #>>42148386 #>>42148471 #
1. iamthepieman ◴[] No.42148386[source]
I agree. I've had this happen often enough on the job that it's not a totally made up example. And usually you'll be one of two or three people in the whole company who is able and willing.

Debugging old DSL vendor specific languages or code so old using, frameworks and standards long out of fashion and support, that they are half way to being a different language.

Adding support for some back ported features or patching security holes in an old client or legacy stacks.

Or at a big company we had some escrow code from a much smaller partner that we ended up becoming responsible for.

Often getting the environment setup for proper debugging is more work than anything.

But yes, it's a good test for a senior+.