Earlier quoted context omitted.
Reciting algorithms is reverse gatekeeping. If an employer wants to grill you on them, get out of there.
Doesn't GOOG go hard in the paint with those questions though?
Like he said. Get out of there.
JavaScript Algorithms and Data Structures (2018)
21–30 of 36 posts
Re: JavaScript Algorithms and Data Structures (2018)
#22Earlier quoted context omitted.
Reciting algorithms is reverse gatekeeping. If an employer wants to grill you on them, get out of there.
Doesn't GOOG go hard in the paint with those questions though?
Not just GOOG, but all of FAANGMULAetc... and smaller start ups as well. Robinhood asked me a dynamic programming leetcode question for their web engineer (front end) role and Bloomberg asked me a OOP design question (asked to code in Python, even though I do not have Python on my resume...interviewer was a Python developer) for a javascript role - both were 1st round phone screens.
The tech industry has normalized to the state of asking such question - its rare to be interviewed on domain expertise, unless you are interviewing at a fortune 500 big corp.
Re: JavaScript Algorithms and Data Structures (2018)
#23Re: JavaScript Algorithms and Data Structures (2018)
#24Do we really need yet another list of algorithms to memorize for interviews? Is another list going to make a better JavaScript engineer? Will help me understand JavaScript better? Will it help me on the job? Will it make me a faster and better React developer? The obvious answer to all of the above rhetorical questions - fuck no. That being said, it is still a topic of interviews, so I will up-vote bc this is pretty…
I've wondered about this -- are such data structures useful? Interviews aside?
Re: JavaScript Algorithms and Data Structures (2018)
#25Is there any practical reason use, say, a linked list from this library vs javaScript's native growable array. You can use unshift() to delete in the middle.
Only the usual reasons to use a linked list. E.g. if you want to store stable references to cells in the linked list as in a linked hash map.
That would be JavaScripts native Map, no?
Re: JavaScript Algorithms and Data Structures (2018)
#26Earlier quoted context omitted.
Only the usual reasons to use a linked list. E.g. if you want to store stable references to cells in the linked list as in a linked hash map.
That would be JavaScripts native Map, no?
TIL ES6 Map is guaranteed to iterate in insertion order. That always made me crazy in C++ too; the structure that I usually actually want is std::unordered_map not std::map.
There are other algorithms and use cases for a stable iteration into an ordered sequence, but I can’t think of any off-hand. It is true that it’s rare to prefer a linked list on modern CPU architecture.
Re: JavaScript Algorithms and Data Structures (2018)
#27Do we really need yet another list of algorithms to memorize for interviews? Is another list going to make a better JavaScript engineer? Will help me understand JavaScript better? Will it help me on the job? Will it make me a faster and better React developer? The obvious answer to all of the above rhetorical questions - fuck no. That being said, it is still a topic of interviews, so I will up-vote bc this is pretty…
I've wondered about this -- are such data structures useful? Interviews aside?
Being able to rattle off exactly how any particular data structure is implemented isn't useful for most developers. Being able to reason about algorithms and data structures _is_ useful in day-to-day development. And that does start with having a basic understanding of some subset of them.
You can clearly see the impact of computational ignorance on the modern web. JS engines have been optimized to hell and back and there are _still_ sites out there that are godawful slow for no good reason at all.
Re: JavaScript Algorithms and Data Structures (2018)
#28[deleted]
Re: JavaScript Algorithms and Data Structures (2018)
#29Earlier quoted context omitted.
I've wondered about this -- are such data structures useful? Interviews aside?
Being able to rattle off exactly how any particular data structure is implemented isn't useful for most developers. Being able to reason about algorithms and data structures _is_ useful in day-to-day development. And that does start with having a basic understanding of some subset of them. You can clearly see the impact of computational ignorance on the modern web. JS engines have been optimized to hell and back and…
[deleted]
Re: JavaScript Algorithms and Data Structures (2018)
#30Similar collection of data structure for JavaScript, with a focus on performance: Mnemonist [1]. [1]: https://yomguithereal.github.io/mnemonist/
Also somehow related prelude [0].