Learn more algorithms not frameworks

Although I agree, I must add - it's not so simple. Learning algorithms pays off in a long run. Learning frameworks is dictated by the imperfect labor market

I'd love to learn algorithms, but where can I find online courses that teaches this in JavaScript?

@drac94 thanks!

or Make your own algorithms.

Or do both. No need to limit yourself. One day, I'm balancing binary trees, the other, trying out ES6 modules, the next, back to implementing merge sort

Meh.

I've never been professionally tasked to implement Dijkstra's pathfinding, R*-tree indexing, Flajolet-Martin's probabilistic cardinality algorithm or even simply a functional and efficient Quicksort.

I've done it because of a mix of boredom and a bit of personal interest, sure -- but it's mostly just taking up useless space in my brain.

Pretty much every imaginable algorithm has been packaged into easy-to-use libraries of "almost perfect wheels", and for the most part, you really don't *need* to know what happens under the hood. Only recognize labels and warning lights.

Those geeky bits of arcane knowledge might make you a slightly better dev, but are only mandatory if you have grandiose ambitions of perfecting the wheel.

For most devs, especially in the first few years, I would say:

Learn one popular language, together with one popular framework.

It makes you employable.

Then, start peeking under the hood of that framework whenever you have questions...

How about both? Are they mutually exclusive?

It's taken a lot of work to learn new frameworks then algorithms. It seems algorithms are only useful in interviews and frameworks are useful in practice.

I came into my new job not knowing kubernetes. And honestly that's been the biggest learning curve, way more than any algorithm they asked during the interview.