←back to thread

Please stop the coding challenges

(blackentropy.bearblog.dev)
261 points CrazyEmi | 1 comments | 15 Nov 24 15:32 UTC | HN request time: 0s | source
Show context
simonw ◴[15 Nov 24 16:00 UTC] 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 #
makk ◴[15 Nov 24 16:07 UTC] No.42148141[source]▶
> Categorizing yourself exclusively as "a Ruby developer" is a career trap.

And a lucrative one at that.

replies(2): >>42148201 #>>42148280 #
rTX5CMRXIfFG ◴[15 Nov 24 16:18 UTC] No.42148280[source]▶
In the short term. And then the entire industry experiences some kind of a technological shift, as it will for many more cycles, and you're jobless as early as the first wave.

It's ridiculous how developers mindlessly accept that you should constantly be learning to keep yourself relevant, but keep it shallow by just jumping from one tool to another, instead of encouraging deeper knowledge of generalizable patterns that stay relevant across waves of technological disruption.

replies(3): >>42148479 #>>42149724 #>>42158777 #
1. makk ◴[16 Nov 24 19:56 UTC] No.42158777[source]▶
Yep. Craftspeople take their craft seriously, sweat the details, learn the patterns, go deep.

And that’s complimentary with marketing oneself as Ruby/Rails dev or whatever else the market needs at the time.