4 ms·
My biggest hope for LLM's was to finally be able to make sense of all the Microsoft documentation; the constant churn in product naming, different versions with
by seemaze 11mo ago
My biggest hope for LLM's was to finally be able to make sense of all the Microsoft documentation; the constant churn in product naming, different versions with varying levels of support and compatibility, the multitude of different API's to accomplish the same operation.. turns out the LLM's are just a confused as me :(
- p1necone 11mo agoEvery single auth related MS library/api I've tried to use has had three different doc pages saying a slightly different version of a slightly different part of what I actually need to know, and then the actual needed information being buried in a stack overflow post somewhere (and that information being slightly different again from the official MS docs).
- wincy 11mo agoStack overflow was wrong then somehow ChatGPT knew what I was talking about when trying to set a dotnet environment variable in azure for an array in an app service. It has to be foo__0 not foo:0 so I broke production in a very nonobvious day for a day. At some point the foo__0 gets transliterated into foo:0 apparently? The absolute worst location for this was, of course, the Azure or dotnet documentation sites. Cmon Microsoft you make both of these products surely this is a huge use case for your customers?
- bigstrat2003 11mo agoTo be fair, that's an improvement over the status quo. Generally they are far more confused than me.
- HugoTea 11mo agoAsking Bing AI anything to do with MS Purview, (which is an M365 product for a range of data security applications), will result in several answers, all wrong and outdated, pointing to documentation that is also wrong and outdated, pointing to other documentation that doesn't exist.