5 ms·
Do 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
by game_the0ry 5y ago
Do 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 good implementation, even though this repo has been submitted to HN at least 4 times in the past.
Someone also mentioned Mnemonist [1] - that one is nice too.
[1] https://news.ycombinator.com/item?id=28957373 https://news.ycombinator.com/item?id=28957373
- Waterluvian 5y agoReciting algorithms is reverse gatekeeping. If an employer wants to grill you on them, get out of there.
- imbnwa 5y agoDoesn't GOOG go hard in the paint with those questions though?
- JasonCannon 5y agoLike he said. Get out of there.
- game_the0ry 5y agoNot 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.
- Waterluvian 5y agoI’ve never been interviewed in any of these nonsense ways. I’m sure it’s popular. But it’s not everywhere.
- diroussel 5y agoAre you saying it’s not important to know what a binary search is? If I interview someone I don’t go deep into algorithms but I want to know that they know how about binary search or hashmaps. Ignorance of these shows ignorance of the basics of computation.
- hungryforcodes 5y agoI've wondered about this -- are such data structures useful? Interviews aside?
- dolni 5y agoBeing 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.
- deleted 5y ago[deleted]
- hungryforcodes 5y agoThanks for your response -- I think you're probably right, but alot of JS's slowness seems to just be all the junk a typical page needs to pull in via HTTPS for all the ads, frameworks and what not. Also videos that autostart themselves, obnoxious pop-ups that take your full screen up after you scroll 20% into an article, etc. That's not necessarily JS's fault. Also algorithms wouldn't help there. :p
- deleted 5y ago[deleted]