eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

211
active users

#readthedocs

0 posts0 participants0 posts today

Divine Documentation

Dad was about my age when he said that reading the manual was better than hypothesis driven button pressing. For teenage me, that took too long. Sure, I may have crashed a computer or two but following my gut got me there. Of course my gut isn’t that smart. In the decades preceding, devices had converged on a common pattern language of buttons. Once learned, the standard grammar of action would reliably deliver me to my destination. 

Image of a nebula taken by the Hubble Telescope.

In programming I was similarly aided by the shared patterns across MATLAB, Python, R, Java, Julia, and even HTML. In the end however, dad was right. Reading documentation is the way. Besides showing correct usage, manuals create a new understanding of my problems. I am able to play with tech thanks to the people that took the effort and the care to create good documentation. This is not limited to code and AI. During the startup years, great handbooks clarified accounting, fundraising, and regulations, areas foreign to me.

I love good documentation and I write documentation. Writing good documentation is hard. It is an exercise in deep empathy with my user. Reaching into the future to give them all they need is part of creating good technology. Often the future user is me and I like it when past me is nice to now me. If an expert Socratic interlocutor is like weight training, documentation is a kindly spirit ancestor parting the mist. 

Maybe it’s something about being this age but now I try to impart good documentation practices to my teams. I also do not discourage pressing buttons to see what happens. Inefficient, but discovery is a fun way to spike interest.

Meanwhile, I’m reading a more basic kind of documentation. Writing English. Having resolved to write more, I’m discovering that words are buttons. Poking them gets me to where I want, but not always. Despite writerly ambitions, the basics are lacking. This became apparent recently when I picked up the book Artful Sentences by Virginia Tufte*. It’s two hundred and seventy pages of wonderful sentences dissected to show their mechanics. I was lost by page 5. The book is, temporarily, in my anti-library. 

So, I’m going to the basics, Strunk and White, and William Zinsser. I’m hoping that Writing to Learn (finished) and On Writing Well (in progress) provide sufficient context about reasons to write to make the most of S&W, for the how, then somewhere down the road, savor Tufte. 

* Those dastardly Tuftes are always making me learn some kind of grammar.

I have asked #GPT-4.0 to translate a news report from Dutch to German for me because I wanted to inform my family about current debates in the Netherlands. I was surprised that #ChatGPT started a #deepsearch although I had not actively selected this feature. I had vaguely heard about it but never used it before, and I am still wondering what it actually does. I will have to #readthedocs for sure! But has anyone got insights they'd like to share? Deep search sounds a lot like #energywaste to me.

I'm in a situation where an organization has a #ReadTheDocs website registered as `<project>.io` (via #NameCheap). Note that no one in this organization are experts or even practitioners of web publishing. People are realizing that the documentation site is not the best landing page and want to do two things:

1. move the documentation site to `docs.<project>.io`
2. set `<project>.io` to host the landing page built on #GitHub with links out to `<project>.io`

The question is: how the heck does one go about doing this without borking everything? It's clear that external links to the documentation would need to change, but in the meantime, I can see the following:

1. register `docs.<project>.io` and add that to the domains in #ReadTheDocs
2. set `<project>.io` as the CNAME for the GitHub site
3. add JavaScript to the 404 page that detects if the link is attempting to point to the documentation site and provide the correct redirect.

Is there anything else that I'm missing? #Web #DNS

Replied in thread

About 2 or 3 years ago, I had some brave soul step up and volunteer to convert the #Xfce #documentation over to the .rst format to publish to #readthedocs

I was busy at the time; but, I went ahead and set up the initial repos & created the workflow that would allow them to publish the docs on the platform.

IIRC, they lasted several weeks and a handful of docs before they disappeared.

It's definitely not glamorous work.😞

I'm seeking experiences in multi-language #documentation, e.g in #Sphinx #SphinxDoc, #MkDocs, …

What system/tool can you recommend? How do you handle contributions in case a person not speaking English (which is the 'main' language) wants to add some section?

The aim is to create docs for #tryton. Thus as a bonus we need/want multi-country docs, too. E.g. for describing country-specific taxing — where we don't need information for France in the English master neither in the German translation, but the German translation needs different parts for Germany, Austria and Switzerland. (And things get worse counting in all the countries speaking English or French.) If you have experiences with this, please share.

Continued thread

Like, I see the benefit of working with rye for setting up new projects and working with well-formed ones, but it's surprisingly difficult to use with #ReadTheDocs because it seems like it wants you to always do things its way and gets upset when you don't.

Okay, #python people, how does one get #rye to work well with #ReadTheDocs?

I'm having a bear of a time because rye complains any time I try to do `rye init` because pyproject.toml exists, but then it complains when I try `rye sync` that it could not write the production lock file....

I just want a `.venv/` folder so that I can run `pip -m install -r docs/requirements.txt` and the python with my #Mac is 3.9, but the project requires 3.10 at least :blobfoxrage:

Continued thread

Part 10: Turns out yesterday was a Reading Day. I have the libraries up and running, but it’s time to truly get the picture as to why USD is even a thing, and what made Apple choose it. A lot of the existing literature is for VFX folks, which I am not, so in addition to my Top Pick references there’s some added color for programmers.

whynotestflight.com/excuses/he

If you watch nothing else (39 min): nvidia.com/en-us/on-demand/ses

Top WAT: developer.nvidia.com/isaac-sim

www.whynotestflight.comHello USD - Part 10: Reading DayA list of distractions