I would point directly at two culprits kind of under the same umbrella -- Google usurping StackOverflow answers in its search results (as in, displaying a Q&A f

I would point directly at two culprits kind of under the same umbrella -- Google usurping StackOverflow answers in its search results (as in, displaying a Q&A format where google's 'answer' is just a portion of a StackOverflow accepted answer) and the general SEO poisoning of search results (ad networks / LLMs scraping and rehosting the content, Google failing to return relevant results etc.) Until seeing this article, though, I hadn't thought about how much I had unconsciously changed my habits to work around the aforementioned issues -- I swapped to DuckDuckGo, started appending site:stackoverflow.com to searches, performing multiple searches around the same content (like grabbing a few keywords from a scraped article and then feeding that into a search of the official documents), and also more aggressively searching GitHub issues With the caveat that I still use SO relatively frequently -- everything from 'I can't remember this specific syntax' to 'I have an intractable terraform/AWS/k8s issue and need to see if anyone else is experiencing it'