>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.
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.
Not Stackoverflow, because all my questions are either ignored or closed, even when extremely detailed and unique.