Data structures and algorithms I actually used while working at tech companies

Re:Data structures and algorithms I actually used while work... by getpost on Wednesday July 15, 2020 @02:22PM (#23849411)

> why hire someone with just look-up skills before hiring someone who really tries, and enjoys the challenge

This attitude will keep you from hiring someone who will just "do the right thing," which is to look up stuff that can be looked up, and also persevere when an off-the-shelf solution won't be sufficient. Plenty of engineers will spend time trying to reinvent the wheel when it is totally unncesssary.

[ Parent | on HN ]

Re:Data structures and algorithms I actually used while work... by foobarian on Wednesday July 15, 2020 @05:38PM (#23852299)

At some point we had a brilliant junior dev who had a task to add some logic to some ES plugins in Java. When the code review went up, it was all a single Java 8 stream statement. He went out of his way to convert everything to a stream because he enjoyed the challenge I guess. It was 3 pages of nested declarations and inscrutable.

He left eventually but person was hard to work with because you had to beat back this kind of shenanigans every step of the way.

[ Parent | on HN ]

Re:Data structures and algorithms I actually used while work... by linza on Wednesday July 15, 2020 @03:54PM (#23850771)

True, but in my experience it's easier to teach resourcefulness after hiring than injecting motivation for solving problems somehow.

[ Parent | on HN ]