@acbdev 🪐✨

Your hard work IS paying off! 🙌

And it's frustrating because in a very important way, the person who wrote the code is the worst person to document it. So the time inefficiency is very high.

The best person to document software is someone eager to get an informal explanation from the person who wrote it.

When I have just written a piece of software, I am literally mentally as far possible from someone who needs the documentation. I know exactly what my software does. I don't have any questions. All features, quirks, and caveats of the interface and any side-effects are equally unsurprising.

To assume the perspective of a person who actually needs to be helped by the docs, to see what could be better with the docs, is far more expensive to the fresh author than anyone else.

I often have set my software aside long enough to start forgetting what it does, or go through several rounds of trying to explain it to others, before I can see what the docs need to be - any docs I previously forced out of myself are usually revealed to be bad once that happens.

I do seem to be getting better at that... the first pass of README for my Python macaddress library still holds up after a few years, I think.

But even so, it's exhausting how time-consuming it is. Does everyone have to take this long? Probably not, but it just rarely comes easy for me. I have to write stuff, re-read it a little bit later, a little fresher, while trying to put on a different mental angle, see flaws - the misinterpretation potentials, the omissions of why it matters, spots where detail or focus is unnecessary, engineer a different wording or examples, rinse and repeat.

YouTube people can be really obnoxious sometimes.

So fuck your tunnels

Fuck your cars

Fuck your rockets

Fuck your cars again

You promised you'd be Tesla

But you're just another Edison

'Cause Tesla broke a patent

All you ever broke were hearts

I can't believe you tore humanity apart

With the very same machines