If creators of documentation are prepared to sacrifice its human purpose in order that LLMs can more effectively slurp it up and regurgitate it on demand, then they have meekly accepted values that more properly belong in a dystopian horror story.
I have just been able to log in to my IMAP account. Only one new message in there, from two minutes ago - which suggests that all messages to me have not even reached the inbox yet.
Some deliveries will be retried, but after 30+ hours some will have permanently failed.
My mail has been coming in slowly since 30 minutes ago.
I am going to give the mail some time to arrive, and then I will migrate my mail to mailbox.org instead.
I have had excellent service and support from Gandi for several years. I appreciated having an EU-based provider that seemed to take pride in having a sustainable approach to the business. There was clarity about pricing. It wasn't the cheapest but they were straightforward and honest in communications.
Every company has an outage now and then, and sometimes a bad one.
But, it has now been 30 hours since I had access to my email. The last update was 15 hours ago. I don't like the way this has been handled.
FAQ lists are the equivalent of the box in my garage where I put things when I've been told to get them out of the house, and I can't actually be bothered to put them in the right place.
Examples in reference material are an excellent idea, and not at all in contradiction to the principles of Diátaxis. An example illustrates - like an illustration in any other reference guide - and provides something concrete to help grasp what's being described.
That's different from a how-to, talking someone through a problem.
Golang API pages collect all examples into a list at the top. Maybe do the same kind of things for stuff like "Quick explanations" and "Warnings/Gotchas". But it would get very subjective and potentially very messy and unmaintainable.