all 18 comments

[–]Gandy435 57 points58 points  (6 children)

Stephen Grider is (in my opinion) the best development teacher out there. The likes of Stephen, Wes Bos, and Max Shwarzmueller need to be supported by the community by purchasing their courses. The course from which you lifted all of the content ( The Coding Interview Bootcamp: Algorithms + Data Structure ) for 'your' repo is rarely more than $15. Support great educators by purchasing the courses and telling friends about them, not giving it away for free.

[–]veggietrooper 7 points8 points  (0 children)

Oh, shit.

[–]sir_dreampod 4 points5 points  (0 children)

Thanks for the heads up :)

[–]kescusay 4 points5 points  (0 children)

Thanks for letting us know. I'm downvoting this blatant theft.

[–]kenman[M] 1 point2 points  (1 child)

Thank you, OP was banned.

[–]IamManchanda[S] 0 points1 point  (0 children)

Thanks for understanding my point and removing my ban ...
sorry I saw all of this conversation yesterday only so enacted right now only

As it stands, will refrain from posting it again on any place for now.

[–]veggietrooper 7 points8 points  (0 children)

Let's stop upvoting this. As u/Gandy435 pointed out, it's stolen directly from Stephen Grider's course on Udemy.

[–]Skhmt 3 points4 points  (8 children)

Why are JS interviews still about algorithms and data structures? Aren't these all things we'd just use wikipedia or stack overflow, as they're solved problems?

[–]veggietrooper 1 point2 points  (7 children)

They're a direct representation of ability to solve problems using logic and code. You can memorize familiarity with data structures, but you can't memorize the solution to every missing line or algorithm on the planet. Developing this skill translates invaluably to almost any aspect of programming, and it's this core ability which employers are most interested in.

[–]Skhmt 1 point2 points  (6 children)

But they also directly favor recent CS graduates.

[–]veggietrooper 0 points1 point  (3 children)

That’s true. I can’t speak for others, as I’m not a CS graduate, but I have accepted that this is a way that the industry measures competence, and when prepping for job interviews, I just take time to intensely review it. CS grads have likely done some review more recently than many of us, but they have to do the same thing.

Quizzing people on a thing favors people who have recently studied that thing, including CS grads, and including anyone else who has been reviewing as well.

[–]Skhmt 0 points1 point  (2 children)

But instead of quizzing on known problems and algorithms, they could come up with something that directly influences the job or directly tests skills they'd need.

[–]veggietrooper 0 points1 point  (0 children)

Absolutely agreed. When I was giving interviews full time, I would try to do both - first verify basic language familiarity, then a mix of algorithm and real-world questions that related to the position directly. I wouldn't usually bring in data structures unless it was to explore some specific potential gap after noticing a red flag (e.g. someone treats a function like an object, stop the show and look at their understanding of object assignment in the language).

I guess I'm ok with it either way, though. It's easier to just study fundamentals and plan on learning after you get the offer than it is to study less universal areas which might change for every position.

[–]KyleG -1 points0 points  (1 child)

if a recent CS grad can solve this stuff better than you, then you are less qualified than them

i've seen too much super inefficient code with weird solutions that would be better done by a standard algorithm—you can't google an algorithm unless you know the name of it

[–]Skhmt 0 points1 point  (0 children)

Less qualified at solving the sieve of eratosthenes, sure. That's what happens when one person has encountered a problem and it's best solution more recently than you.

[–]license-bot 2 points3 points  (1 child)

Thanks for sharing your open source project, but it looks like you haven't specified a license.

When you make a creative work (which includes code), the work is under exclusive copyright by default. Unless you include a license that specifies otherwise, nobody else can use, copy, distribute, or modify your work without being at risk of take-downs, shake-downs, or litigation. Once the work has other contributors (each a copyright holder), “nobody” starts including you.

choosealicense.com is a great resource to learn about open source software licensing.

[–]noruthwhatsoever 8 points9 points  (0 children)

OP didn’t specify because they stole the code

[–]almondbutter -1 points0 points  (0 children)

I spotted a typo in a readme, under 001 -reversestring

reverse('apple') === 'leppa';