zlacker

I mean.. if you can finish a task for a client in a day, and someone else needs two days, isn't that a huge difference? Or to turn it around, if someone does 10%, 20%, 50% more in the same time period, isn't that significant?

I mean.. we are comparing students abilities here, and doing stuff fast is one of those abilities. Even potato peelers in a restaurant are valued more if they're faster, why not programmers too? Or DMV workers?

>>ajsnig+(OP)
I don't think test speed is correlated with that.

Like anything i had to do in a test when i was taking my CS degree is maybe 5% if not less of the portion of my real job tasks. Even if i was triple as fast at taking those tests, i think that would be a neglibile increase in on the job speed.

>>ajsnig+(OP)
"I mean.. if you can finish a task for a client in a day, and someone else needs two days, isn't that a huge difference?"

I've never seen that come down to processing speed. Even as a programmer -- I can program probably 10x faster than most of my peers in straight programming contest style programs. But in terms of actual real work -- I'm probably slightly faster. But my value is really I spend a lot of time really understanding the ask and impact of the work I'm doing -- asking good questions, articulating what I'm delivering, etc...

That is, my faster processing speed results in very little added benefit. That is, time to deliver results can matter. Processing speed typically is a very small percentage of that time. And for these tests processing speed is often the main distinction. It's not like they're distinguishing one kid who can't solve this equation and another kid who can. It's generally more likely one kid can finish all 25 questions in 32 minutes and the other would take 38 minutes so they only finish 23 of them in the allotted 32. I don't think that ends up mattering in any real way.

>>kenjac+Z3
I'm always surprised by comments like the gp's. Even working on different types of programming jobs I would be surprised if the majority of time is spent on actually writing lines. The majority of my time is spent on understanding the codebase and how the new requirements best fit in there. I do see people jumping in straight to /a/ solution, but every time I've seen that happen it is hacky and ends up creating more problems than solutions.

I'm also surprised at how common it is for people to openly discuss how irrelevant leetcode is to the actual work on the job but how it is still the status quo. On one hand we like to claim that an academic education is not beneficial but in the other hand use it as the main testing method.

I think why I'm most surprised is we, more than most other jobs, have a publicly visible "proof of competence." Most of us have git repos that are publicly available! I can totally understand that this isn't universal, but in very few industries is there such a publicly visible record of work. Who else has that? Artists? I'm not sure why this isn't more heavily weighted than these weird code tests that we've developed a secondary market to help people optimize for. It feels like a huge waste of money and time.