I was listening to the Programming Touchdown podcast, and on Episode 43, around the 13:00 minute mark, there was the following quote:
I can count on one, maybe two hands, the number of times in my entire career where I need to use… like the algorithm I used made an impactful difference. Most of the time, it doesn’t matter, architecture can matter, sometimes. Like, true, textbook algorithms.
This is roughly what it felt like to hear this…
I mean, seriously! Okay, I write database engines for a living. Part of my job is to look at academic literature to see if there are good ways to improve what we are doing. But you know what, let us say that building database engines is something special, and that your regular web developer doesn’t need any of it.
Let us see how right that is, shall we?
- Data structure - Stack, Queues, Linked Lists, Arrays, Binary Trees.
- Concepts: Co-routines (async in C#, promises in JS, etc), Random Numbers, how floating points number actually work.
- Sorting algorithms, searching sorted & unsorted data.
Saying that algorithms don’t matter is about taking decades of research and throwing it down the tube, because the machine is powerful enough for me to not notice that I’m brute forcing a solution at O(N**2)