As a fullstack developer most of these things are not needed. Having a good understanding of what is optimal is good, but you shouldn't have to be able to rec

As a fullstack developer most of these things are not needed. Having a good understanding of what is optimal is good, but you shouldn't have to be able to recite all the big O notation. Funnily enough none of the tests I've had ever talk about relevant things like data normalisation / de-normalisation or anything that will be used in the project.