Not knowing BFS is not just ok, it's better for problem solving. You should not be training your brain to remember specific names of complex algorithms. You should be training your brain to think in primitives, in basic algorithms and data structures and be able to naturally get to BFS without knowing what it is when it fits the problem well. At least if you want to be a programmer and not a master of interviews. Don't take pride in knowing terminology. Terminology comes naturally after working for some time in the domain.
in college, this was "don't memorize anything for physics exams, because you can derive everything from a small number of basic physical principles".
First principles
No one asks a mechanical engineer to white board FEA or integrate by parts. Everyone just accepts that an experienced engineer will be rusty about things outside his career domain.
Well, that was college. If you want a job with Google (or the companies that try to mindlessly mimic their hiring process) --
your best bet is to memorize.
yes, when I got my job at google I had basically memorized CLR (I was a biologist, not a computer scientist, so I had to do a bunch of extra reading).
Except this wasn't was an "algorithm researcher" position he was applying to.
It was, you know, a programming position.
I'm pretty sure that no one has a opening to research how to find the area under a simple curve.
If you can find an aspect of frontend development even remotely analogous to integral calculus, LMK.
tensorflow.js?
That's an application. Not a matter intrinsic to frontend development.