The others aren't that interesting if you aren't dealing with hardware, and their function is obvious if you know the naming convention.
((a or b) is (not ((not a) and (not b))), and vice versa.)
Example, most programmers I know have no idea when a variable gets allocated on the stack and when it's on the heap.
Let's not talk about how many dont even know what a (stack overflow)[https://en.m.wikipedia.org/wiki/Stack_buffer_overflow] is...
It’s possible the undergrad assumed you were referring to an efficient recursive algorithm or simply forgot most recursion.
if (i<=1)
return i;
else
return factorial(i-1)*i;
It wasn't meant to be a trick or trap, it was the simplest recursive function I could think of and it’s not like I was asking him to implement a stack.Probably won't get an offer because of that. Do I feel like as a frontend engineer I really need that knowledge? Not really. I could work it out for work purposes if I needed to tho. I'd be practicing it just to pass interviews.