As someone who has been programming in Rust since before 1.0, I have been through the probably rare experience of working with an un-Googleable language. I reli

As someone who has been programming in Rust since before 1.0, I have been through the probably rare experience of working with an un-Googleable language. I relied solely on docs and occasionally the mercy of helpful folks on IRC, and it turned out OK. A side effect of this is that I still never Google for Rust answers, even though there are tons to be found now. However, if I was programming in Javascript, which has been the language I've known for the longest and done the most in, I would still Google everything because I'm lazy. I'm pretty sure I don't need to, it's just faster. It's possible to be a Google-programmer out of laziness and not necessity. Diving into an un-googleable language (or ecosystem -- many closed-source ecosystems at work would be un-googleable or undocumented; I recall that understanding the codebase for my internship required me to either read tons of code or ask people with arcane inside knowledge) can help hone these skills. Or just promise to not use Google for something.