3 ms·
This list is very funny, straight out of the 90s, because we are in 2017 and most developers just spend their working days basically writing forms and storing/f
by invaliduser 10y ago
This list is very funny, straight out of the 90s, because we are in 2017 and most developers just spend their working days basically writing forms and storing/fetching data over the network/in a database.
- bryanrasmussen 10y agoI don't know if most developers still do an awful lot of that. At least not for the jobs I do - I do some but it's probably less than 25% of what I do. And anyway if you have gotten the data you often need to do something with the data and sometimes that includes sorting it or other stuff.
- invaliduser 10y agoBesides calling Array.sort()? When was the last time a front-end developer, or an app developer, or any developer actually, needed to implement a sort algorithm? I started programming in the 90s, so I did a lot of it, implemented sorts, btrees, tries, you name it. When was the last time I need to implement it? Honestly, it's been a very long time, around 10 years, and it was just a bloom filter in c++ because it's not very used and few libraries have it. Could I provide an implementation in an interview situation? Nope. And not interested in using my poor memory for it. If I ever need to implement a specific algorithm, say in a new language in which nobody did it before, I just need to make a search on google, take a few minutes to study it (for a sort), or hours (for more complex structures like btrees or algorithms I never used before), and use my knowledge/experience. Of course, I don't need to implement those algorithms, but I use them a lot, everywhere. That's where interview questions should focus, where and when to use them appropriately, because that's the business case.