DEV Community

Adam Crockett 🌀
Adam Crockett 🌀

Posted on

I know what it is, I just don't know it's name.

I get this feeling quite often, I am a seasoned programmer who has stopped trying to learn everything. The result is a lot more space in my ram headspace for my life and family.

The downside of not knowing everything comes from the root of why I'm a programmer and not a math guy, I don't need to know the answer I need to know the question, this means I need x? To get result, but what is x called again? I used it last year, ummm it begins with R... And so on and so fourth, googling a few rough description to find leads for the name of the thing that I need. Is that you? I'm here to tell you that I have no answer for this, it's just part of being human.

Top comments (2)

kendalmintcode profile image
Rob Kendal {{☕}}

This is so weird, I was talking about a very similar thing with a podcast guest this morning, and the difference between learning and memorising (the latter of which, I suck at).

Had this in a gruelling technical interview recently where they were throwing acronyms at me and I only managed to get like 50% of them right. But I absolutely get what you're saying and suffer the same thing!

connoravo profile image

I suffer a similar problem. If it's not something I commonly use I don't tend to retain the information but more remember the name or description of what solved my problem.
I've thrown up a quick hugo site for myself, so when I use something that I don't quite use every day, I can make a record and simply tag it in such a way that it's easier to find again, rather than Googling.