zlacker

>>azhenl+(OP)
Having participated in competitive programming and comparing it to development work it feels to me comparing chess tactic puzzles to classical chess. If you're a good classical player you're probably reasonably good at puzzles, but the opposite is not necessarily true.

Competitive coding, despite superficially involving typing code into an editor, has almost nothing to do with working on large pieces of software. It's a lot of rote memorisation, learning algorithms, matching them onto very particular problems, and so on, it's more of a sport. Just like playing too much bullet chess can be bad for your classical chess I can honestly see how it gets into the way of collaborative work.

>>Barrin+72
I was very good at competitions, but terrible at rote memorization, including memorizing algorithms and matching them to particular problems. I'd just create the algorithms on the fly. E.g. I was presented with a maze solving problem, never had read about maze solving before, and just created my own version of it.

It's easy to make generalizations that minimize or downplay some of these things. But it's no more knowledge then the original study on too little data was.