Today I had an issue and I also had a solution in mind, but I still used SO to find alternative solutions, in the end others had same workaround solution as me but sould have been great for my case if the workaround was not needed.

IMO "use the documentation" is not enough, many times you have much more complex question or bugs/problems where if lucky other individuals hit them before you and were kind enough to share their findings. I upgraded my Ubuntu version and now some people decided that is safer and smarter to move the /tmp in apache to some other place but at the same time hide it from me, I am not sure what man page search query for "my file is not in /tmp but the system is telling me is there" will give you the results.

Not sure if apache or systemd are to blame, or security extremists, but I hate this kind of magic, please crash my app with a clear message instead of doing shit behind my back and showing me fake reality.

I intentionally avoid SO. The S/N ratio is terrible.

How frequent you refer SO depends on simply how crowded the field you're working, and nothing else.

I bet you don't work mainly in C# or Javascript. (Or, well, Javascript SO has been downhill for a while, so maybe it's time to take it out of this list. I wouldn't know.)

On some stacks, you depend on SO for everything. Others have much more complete and usable documentation somewhere else that answers any question that SO would accept, so people don't need it at all.

I work with C# and I almost never use stackoverflow anymore. Back in 2013 when I started working with it I remember I would use stackoverflow every day. But now I find way more answers in github issues. The answers on stackoverflow are usually really dated if they exist at all. Its almost like when microsoft made the move to dotnetcore and started hosting the project on github all the dotnet related activity on stackoverflow stopped.

It's not that it has stopped, but there is less and less open topics where there is no solution. And those topics are usually (in my experience) niche topics and will get better discussion in GitHub issues or in a similar system. Or related to a legacy stuff, then SO could help.

In addition to that, quality of experience, code, as well as quality of documentation increased comparing to before .net core. I find myself often going to the official docs for documentation now, or just look in the sources or even debug the internals using available debug symbols.

Interesting. Granted, I never looked at the .net github itself.

Github issues have also largely replaced SO for me when it comes to failure modes (production tasks). But it's relevant for development when you want to learn how to extract a certain behaviour from a given tool. It's a treasure trove of obscure capabilities, especially when it comes to older versions of tools you've got to work with in production.

Same. I've downloaded most of the documentation I need to answer day to day questions, and try to limit my use of search engines. Finding most of my answers is faster in the local references I'm familiar. The Internet is my last resort.

Can I ask you what workflow you use for this? Any particular tools? What do you do for documentation that doesn't provide a download?

I use Dash on my Mac for most of the documentation. It makes searching any of the "docsets" it has indexed fast. I've recently started creating some of my own.

I save references I use a lot, like the HTML spec, as PDFs. MacOS indexes these PDF files, so a search in Finder is usually all I need to bring the correct document.

If I can't find a reference locally, or know it doesn't exist locally, I'll turn to the Internet. Once I find the bit of information I'm looking for I'll either save the website as a PDF, or save the info in Snippetlabs or Bear so I can search for it next time I need it.

But GitHub doesn't offer its source code. Did you mean to say just "source code"?

It was floating over HN last year, I guess gp has kept it.

We can't all be 100x, God's gift to computer science, engineers like you.

All it takes to be a 100x engineer these days is to read actual source/docs?