I google a lot in my job as well, but one thing I’m trying to do is reduce the number of repetitive searches I do and remembering what to do afterwards. I think part of personal development is learning how to do something and not relying on google or any other reference because as we’re all aware they’re will be a time when stack overflow or GitHub goes down.
I've been trying to do almost the opposite: as I gain experience, the number of tools that I want to be able to use keeps getting bigger, which makes it unreasonable for me to try to remember the details of how to use any of them.
I make a lot of my own notes ( https://til.simonwillison.net/ ) but I also rely very heavily on Google, and I'm fine with that.
I think a good way of looking at it is like the knowledge circles where everything inside the circle is stuff you don’t google but everything outside is things you do. Over time the circle expands as you learn more but this leads to more things you need to google.
The issue with notes is when the solution changes because of an update. Using Google and grabbing recent solutions gets you updated answers if and when things change.
I try to find the balance between both of these options. I think it’s important to remember that just because someone wrote a blog post recently doesn’t mean it’s better. It also depends what you consider “core” knowledge, as an example I don’t need to google how to rebase anymore but I sure as heck do google something new about git every week.
Sigh... searching is redundant, not guaranteed to be sorted the same, not guaranteed to be up-to-date, and updates are not guaranteed to be correct. your notes will last forever, whether or not the software changes under your feet.
I (try to) take notes, and look around once i see a deprecation warning.
> I google a lot in my job as well, but one thing I’m trying to do is reduce the number of repetitive searches I do and remembering what to do afterwards. I think part of personal development is learning how to do something and not relying on google or any other reference because as we’re all aware they’re will be a time when stack overflow or GitHub goes down.
For me, it really helps to blog with code snippets, annotations and full explanations.
I use git diff > iteration123.patch then copy-paste to OneNote along with a quick summary of my thought process.
It really helps me to retain what I've learned (and it reassures me that I can account for how I'm spending the considerable self-learning time I'm being given during my current internship)
