2 ms·
> Some of the interviewees have been developing for over a decade and can't say what a linked list is, let alone contrast it with vector or an array. Jaw dropp
by javajosh 12y ago
> Some of the interviewees have been developing for over a decade and can't say what a linked list is, let alone contrast it with vector or an array.
Jaw dropping. Some degree of this is acceptable - e.g. I wouldn't really expect a front-end dev to know browser-native DOM manipulation, because everyone uses some sort of shim (particularly jQuery), and modern-modern frameworks abstract away DOM manipulation entirely (think React). But that's a high-level API trade-off, rather than a foundational issue. OTOH it's far more serious when a dev doesn't know about Array.forEach and insists on using $.each for iteration, showing an inability to distinguish between native JS and jQuery.
Part of the problem with JS and data structures in particular is that, AFAIK, there is not even a de facto collections standard. Google's Closure structs[1] might come the closest, but generally brings a lot of baggage. js_cols[2] is pretty good. And then you have what I would consider "fringe" solutions like mori[3]. The bottom line is that even an autodidactic developer starting off in JavaScript land is going to have a much harder time learning about basic data structures than if they started off in Java land, which, while it has it's warts, does have a wonderful standard library for collections[4].
[1] http://docs.closure-library.googlecode.com/git/namespace_goog_structs.html http://docs.closure-library.googlecode.com/git/namespace_goo...
[2] https://code.google.com/p/jscols/ https://code.google.com/p/jscols/
[3] https://github.com/swannodette/mori https://github.com/swannodette/mori
[4] http://docs.oracle.com/javase/tutorial/collections/index.html http://docs.oracle.com/javase/tutorial/collections/index.htm...