No one’s mentioned the obvious here. We have computers so we don’t have to remember basic things. It’s far more useful to know a thing exists and what words wil

No one’s mentioned the obvious here. We have computers so we don’t have to remember basic things. It’s far more useful to know a thing exists and what words will help you search for it. Being able to build things through first principles will mean you understand things better, but doesn’t make it required. It’s not clear to me why you are implementing things that should already exist in a library, but I will say, if you are slower than coworkers, and that this is indeed a problem, then turn it into a strength. I have a sort of mild dislexia, where I tend to confuse my perspective. For example, am I looking at a local minimum or a local maximum? The plus side is I’m super creative, but the down side is I have to constantly make sure to double check my work. As a result, I can be much slower developing software, but because I’m paranoid, my code tends to be less bug prone. What I’m trying to say, is if you find you’re slower than coworkers, then make sure your quality is higher as a byproduct of this slowness. The main thing about work, is it’s literally not a competition, teams work better when we each work to our strengths.