[Etheryte]

I can see where you might get that sentiment, but where do you plan to go when new tech rolls around, the docs don't cut it and your LLM of choice hallucinates APIs that don't exist? This was always Stackoverflow's bread and butter, and people who only use it as noob search tend to miss that fact. SO can be a tough crowd, yes, but mostly it's people who didn't read the rules before posting who get burnt. That aside, it still has a very high concentration of experts that you'll struggle to find anywhere else.

[protocolture]

>I can see where you might get that sentiment, but where do you plan to go when new tech rolls around, the docs don't cut it and your LLM of choice hallucinates APIs that don't exist?

Not Stackoverflow, because all my questions are either ignored or closed, even when extremely detailed and unique.

[LtWorf]

> even when extremely detailed and unique.

or so you claim.

[protocolture]

Well my last attempt turned out to be a vendor issue. It was officially acknowledged by a vendor support rep. It had to do with their unique method of populating a whitelist with DNS entries, and weird response chain to blocks in that state.

I read through the backlog, ensured I had completely exhausted every other avenue (short of 3 more weeks of yelling at one of the involved vendors for information about how they were performing their whitelisting) and had available captures for network and application, full reproducibility steps and details of everything that had been interrogated. I even remember linking similar issues, and explaining how I ruled out their causes.

In fact I am still relatively confident that the way mobile browsers were responding to the bug, probably constitutes a bug in itself but honestly, cant be assed to pursue it.

When enough time has passed I will probably produce a blog about the issue, so it can be digested by the next iteration of the troubleshooting machine. But I really dont feel compelled to provide further data to the stackoverflow community directly considering their complete lack of response. Even closing it as a duplicate of an existing issue would have been helpful, but it wasn't a duplicate so it was just ignored.

[SwiftyBug]

Unfortunately the answer to that is the Discord server of whatever technology I'm working with. Communities are now separated each in their silo on Discord, far away from the public internet, where nothing can be indexed.

[JustExAWS]

Most of my work these days are around the AWS SDKs and Terraform. I always just say “verify the APis on the internet”.

Now, AWS has a documentation MCP server that can integrate with ChatGPT.

https://github.com/awslabs/mcp/tree/main/src/aws-api-mcp-ser...

I haven’t used it.

[rafark]

> the docs don't cut it

Yet. By the time stackoverlow shuts down, AIs will be powerful enough to take data from docs or just from the source code alone. I mean the new version of opus is pretty good at understanding my front end source code. I think that should be the goal of AIs (that they are so advanced they don’t need to read code examples from a third party website like stackoverflow)

[Etheryte]

This is a pretty narrow view. Most APIs out there are not source available, frontend libraries are the odd one out in that regard. Likewise for docs, it doesn't matter if the LLM can read the docs or not if the docs literally don't include the things you need to figure out. I suspect this is a generational divide, people who grew up with SO can't imagine what life was like before it, but right now we're on a straight course back to isolationist communities, if we aren't already there.

[rafark]

Really? That’s actually a very narrow view to think that AIs need to rely on code examples of some third party forum.

AIs will be good enough to understand the docs and source code alone, just like the human answering a stackoverflow question.

[arbol]

LLM clients like chatgpt can scrape the code of new tech on demand. They tend not to hallucinate when you provide fixed inputs like this.

[John7878781]

While LLMs may have used Stack Overflow data to get their start, I think it's reasonable to assume that this source of training data will no longer continue to be useful.

Therefore, as both a data source and a QA website, Stack Overflow has lost its relevance.

[memset]

The source code itself.

If an LLM can read the source of the library you’re trying to use - or examples of others using the library in GitHub, or official documentation - then there is less of a need for a fellow SOer to put the pieces together to debug issues and answer questions.