I don't think there is that much value in memorizing rarely used, easily looked up information.
Facts alone are like pebbles on a beach, far better (IMO) to have a few stones mortared with understanding to make a building of knowledge. A fanciful metaphor but you know ...
(Can't say time is the limiting factor either -- we're both in HN comments, valuing our own time at zero.)
And of course, what if your phone dies?
There is limited time, of course - no one can learn everything, but you can pay attention to the important facts, and the connections between them.
In some ideal world you would learn every fact there is, and the connections would fall out on their own, but in the real world we have to construct theories and frameworks to organise facts.
Let's for example about html boilerplate, where you don't remember the syntax. What you remember is the components & why they are needed, then add them one by one as you recall your memory. Doctype, html tag, head, body, etc. It works because html is simple and common.
Then for express it is harder, because you need to recall javascript syntaxes and express syntaxes, and most of the time you don't get involved with express outside req and res. You recall that express need body parser, register routers, and finally listen, whether you use http server first or directly from express. Now you compose one by one, looking at docs or web for the forgotten pieces, but you don't lose the understanding / logic of express, you just forget the syntaxes.
As for stream where I keep forgetting it, I just need to remember that stream need source, event handler such as on data, error, finish / end. Pipe if needed. However I never remember whether to use writable, readable, streamable, etc because I seldom get involved with them, and can look up for references anytime.
To use another metaphor, you can't REALLY see the forest amongst the trees, if you don't consider the trees themselves.
One of the reasons I like history so much is because, with enough facts accumulated, you can see how one piece of information flows into another - e.g. dates matter, because knowing the precise order in which important events occur helps you determine how those events may or may not have affected each other in the course of their unfolding.
Sure memorizing dates is boring on its own, but putting them in contexts is exciting - you still need to comb the beaches to find the right stones!
I guess an interesting counterpoint to what I said is something like https://en.wikipedia.org/wiki/Phantom_time_conspiracy_theory (and similar) where a grandiose framework tries to fit inconvenient facts into a shape that is entirely invented.
easily looked up - we don't have that any more since Google decided to entshittify search. What you now have is not looked up information, as that would look the same each time you "looked it up" - instead of a quick 3-4 word search pattern you now write an elaborate verbose "query", and get a chewed up re-interpretation by the shitty LLMs. And then since sometimes its not quite what you asked for, you have to ask it again or redirect it and just like that, you've wasted 5 mins of your time arguing with a goddamn neural network!
> Yet I can code normally provided there's internet accessible.
I'm the opposite. Yes I need my computer to test things fully, but I'm able to code on paper. I want my computer to be a complete sufficient node, so I mostly install documentation and my computer is mostly not connected to the internet, unless I actively enable it to do a specific thing.