4 ms·
This just smacks of defensive justification for lack of participation. "I don't do this and I don't want to do this, so I'm going to bash it and the people who
by diminoten 12y ago
This just smacks of defensive justification for lack of participation. "I don't do this and I don't want to do this, so I'm going to bash it and the people who do it so I can pretend I'm making a choice instead of just being lazy". It's a little bit like the folks who say, "I'm saving myself for marriage" when in reality they've never been on a date in their lives.
Pretending like people can't think in more than one mindset is an inaccurate model. I've never done an honest-to-goodness coding competition, but I can imagine someone who does code competitively to think very differently when they're competing vs. when they're designing/implementing a solution as a professional endeavor.
Someone would have to explain to me in much more detail how this "negative correlation" is established before I believe it.
- zodiac 12y ago> Someone would have to explain to me in much more detail how this "negative correlation" is established I think it's just a statistical correlation they found in the hiring data.
- diminoten 12y agoI'd need to know more about the hiring data, the actual correlation method, how they collected the data, what was the sample size... Basically, like I wrote, I would need to know more.
- collyw 12y agoI have refused to do a couple of time pressure hacker rank challenges as part of a job interviews recently, as it is not how I work on a day to day basis. I was good at these sort of things fresh out of university 15 years ago. I have never had to implement any algorithm under time pressure in my professional career.
- diminoten 12y agoWhy must it be "how you work on a day to day basis"? Why must interviews only be about exactly what you're being hired to do?
- collyw 12y agoI would like to think it is at least somewhat related to what I am doing, rather than a lucky dip of a question that I might get or might not. I am a way better software engineer than 15 years ago, yet I am worse at these sort of "challenges".
- diminoten 12y agoThere's a lot more to being a software engineer than coding competence, and timed questions reveal the non-coding competence parts of your abilities more than anything else. Perhaps you're not as good as you think.
- jschwartzi 12y agoLike what?
- diminoten 12y agoSeriously? Less than half of a software engineer's daily work is actually coding.
- jschwartzi 12y agoI mean what other components of your competence do the timed coding exercises reveal?