As a developer, I agree. When coding, I look for three things: - well-written blog articles A single article, describing a real dev solving a real business ch

As a developer, I agree. When coding, I look for three things: - well-written blog articles A single article, describing a real dev solving a real business challenge with real code, is the best way to answer technical questions. They provide a lot of context, and reasoning, and have real-world advice which is invaluable to me. I use Google for this, but it requires care. A lot of sites are poorly written, or copied from other sites, or are gibberish. With experience you can quickly tell if a blog post is going to be of high enough quality or not. - short answers, or reference documentation Google/StackOverflow is okay to answer the question "I have tech X and want Y using library Z". Just recently I've switched to asking GitHub Copilot for answers to small questions. It's not perfect but incredibly valuable. The big downside is since Copilot sends code to a server, it's not okay when working with client code. Copilot is great for learning, though. For reference docs I use Google to find manpage sites, then I setup custom searches for them. Example: https://man.cx/ https://man.cx/ for Linux docs, and https://ss64.com/osx/ https://ss64.com/osx/ for macOS. There's also https://devdocs.io/ https://devdocs.io/ which is incredibly fast but too webdev-centric compared to my normal work. - example code This site is magic! Incredibly useful source code search engine: https://grep.app/ https://grep.app/ Example: Kubernetes manifests can be complex and mysterious. The following produces 250,000(!) Kubernetes YAML manifests for study. Enjoy! https://grep.app/search?q=apiVersion%3A&words=true&filter[lang][0]=YAML https://grep.app/search?q=apiVersion%3A&words=true&filter[la...