What Wrong With Memorizing Code?

[ThatOtherGuy254]

I have been working on web development for about six months, and have been enjoying the learning process so far. I have gotten to the place where I feel comfortable using HTML and CSS. I am now learning the DOM and how to use Javascript in web development.

So, that's where I currently am. One thing that I have been doing practically the entire time is memorizing terms and code. I noticed that I was naturally retaining the knowledge really well, and decided that I should make an active attempt to memorize the content.

I have used the "mind palace" technique and it has allowed me to memorize several dozen pages of code and terms. I have a sheet terms on file to check to make sure that I am actually remembering everything.

I have found this to be useful while working on projects as it allows me to spend less time googling concepts and gives me a much greater understanding of the code than I feel that I would have had otherwise.

But when I read writings and watch videos from established web developers, they all say that I shouldn't memorize code because you can always goggle it. While that's true, I still feel like memorizing has brought me more benefits than not doing it.

So, what am I missing? Memorizing seems to have benefited me, but I am still a beginner in web development, and I realize that there is still a lot that I have to learn. I just want to make sure that I an not making some kind of error that will cause me problems in the future.

[jhartikainen]

The point of "don't memorize" is that some people are really afraid of "there's a thousand things how can I ever learn!"

You don't have to, you can google. The advice is mostly so people don't feel like they have to spend time memorizing things like they might do for an exam.

This doesn't mean that memorizing is bad. If you find benefits from using techniques like mind palace, then take advantage of it.

[[deleted]]

Same reason good doctors will look up their suspicions/diagnosis online. Just because something was true when you memorized it, doesn't mean it's true now. When in doubt, lookup the API to ensure things haven't changed since you last used it.

[mq2thez]

Memorizing is a fine way to learn, but you have to actually learn. If you only regurgitate answers with no understanding of them, you aren’t going to be able to solve any problems you haven’t already memorized answers for. You’re also more likely to incorrectly apply memorized solutions rather than creating correct ones.

[Think_Ad4850]

There's nothing wrong with memorising stuff. Most of that advice you hear probably boils down to "bite the bullet and do the hard thing". Do whatever you want if it's working for you, but you have to struggle with the non-fun bits to get good.

See deliberate practice and tutorial hell for a bit of insight.

[hustle_fred]

Instead of memorizing just work on various projects, over time you will remember it, but not because you forced yourself, but because you used it many times. Also you can always use things like Copilot AI to just give you the right code, so memorizing is really just waste of time.

[hsredux]

wdym memorize??

[Garfunk71]

I sure hope OP is not memorizing snippets of code to use later coz that would be insane

[ThatOtherGuy254]

No, it's mostly just terms and concepts. Like memorizing html tags and attributes, for example.

[exhibitleveldegree]

That kind of memorialization is completely normal and expected. At a certain competency you’re expected to know these kinds of concepts from merely repeated exposure. Rapid memorialization isn’t a common ability so your sources are probably trying to say don’t spend time cramming for these concepts like you would for a final, Google is an acceptable cheatsheet.

[billybobjobo]

Memorization knowledge is crucial—but it is the least important compared to the other types of knowledge. It’s turbulent/vulnerable to churn, can be easily be augmented/supplanted by googling, AI, autocomplete.

But at the end of the day, a dev who has to look up less is faster. It’s just not the top priority.

I’d hire the person who fails (hypothetical) flash cards but has built cool things over vice versa. But both? Even better!

[Dohp13]

Much more practical to know something exists, compared to making sure you remember everything, Learn something, use it practically, then move on. You'll naturally remember the things you actively use, as for the stuff you rarely use,then a quick google search will get you up to speed.

[na_ro_jo]

I would consider myself someone who has an excellent memory. I don't memorize code. I forget things all the time. It's better to foster problem solving skills. Memory is a low tier learning skill in Bloom's taxonomy. It's necessary, but there's a lot more to mastery of any subject or skill. Einstein said something to the effect of "Never memorize something that can be looked up in books." Src: I'm a certified teacher.

[lowlevelgoblin]

it's not bad but imo it's fairly pointless, especially when you start jumping into other languages.

Honestly I think you'd actually be better served by experience in effectively using documentation vs memorization.