As a new developer, this is what I am doing and focusing at. Not be reliant on the internet and it works. Because I have several books and for example I can read Mozilla MDN offline.
I use a website/app and books, the website updates itself. But for some things I still need to look elsewhere than Mozilla MDN, e.g W3.org
Mozilla MDN is pretty much the last thing I’d prioritize for offline reading, since it’s relevance is tightly coupled to the availability of the network.
I might prioritize offline resources for Raspberry Pi and other computing platforms, that make more sense without the Internet.
But above that, maybe a few books about growing food in one’s own garden. :-)
There's a difference of building a reference library for home use or homesteading, crafting, etc than say working for 8 hours on a coding project directly tied to the need to use the computer. Computer languages/libraries/etc change frequently enough printed books become obsolete fast. How/when to plant, what to feed them, etc hasn't changed too much for generations. Nor things like when to use a dovetail joint, or other building techniques. Books from the 1900s would be just as useful today.
Nowadays I've always discovered that I'm not the first person to ask.
Just a small example, I imagine there are a lot of JS developers who know that they need to create a new function using “=>” or “.bind(this)” if they need access to “this” within the function… and if they don’t, things break, without really knowing why (even though they know the solution).
TLDR: the best developers I’ve worked with go beyond “knowing the solution” to “knowing why the solution is the solution”. Understanding “why” something is the way it is becomes difficult when something like Copilot autocompletes the correct answer.
Sometimes pulling an all nighter and beating your head on the wall is less productive than just stopping to take a break and coming back at it with a fresh mind. FAANG PMs don't get this and probably think less of you because your Zen like approach is anathema to their fast paced do or die approach now. You can't be productive if your butt isn't in the chair.
Literally went to the library to read books on IR and make sure I understood what the doc was saying. Asked around to find people who worked on these kind of sequencing. Went to a small repair shop and bribed the tech to give me hints on how remotes work.
It was fun in retrospect, maddening and incredibly taxing at the time.
I don't think we did anything fundamentally wrong, short of underestimating the problem space. It's also not as if I was left in my corner for weeks, I got pretty good advices (like go finding more help and returning to basics). Getting info before the internet, before makers got into habits of published maintenance manuals etc. life was just way harder.
But it was less stressful, because you didn't have daily standups and biweekly sprints.
More generally speaking, most people today would be incredibly frustrated getting information about anything generally if they were plopped down 30 years ago. When I was a product manager back then, we paid consulting companies large sums of money to get the most basic competitive information faxed to us because you couldn't just look it up.