Re:Why HackerRank and other coding tests are ageist
by openmosix on Wednesday September 06, 2017 @01:06PM
(#15185252)
Things evolve. The scale of problems evolve. A data structure that was handling hundred of transactions, crumbles on hundred of thousands. Premature optimizations (and premature abstractions) are the root of all evil.
[ Parent
| on HN ]
Re:Why HackerRank and other coding tests are ageist
by shados on Wednesday September 06, 2017 @11:17PM
(#15188927)
No argument there, but that's not what I'm arguing.
Do you have to reach out for google or a book to do a simple if/else statement? What about a for loop? Now what about the difference between a map and a set? Likely not, it's the basics used in any app.
Talking about premature optimization here implies there's some work to be done, things to think through, stuff that's not obvious. And that's totally true at a certain complexity level.
But what is "complex" and what is "obvious" isn't objective. It's purely a factor of what the "average software developer" knows.
What I'm arguing is that while at one point the pendulum was swinging too far one way, it's now too far in the other, and it's affecting software quality industry wide.
Re:Why HackerRank and other coding tests are ageist
by AstralStorm on Wednesday September 06, 2017 @01:44PM
(#15185603)
Corollary: A data structure that is instantiated million times in small sizes is different from one huge instance with million entries.