@Bluedepth You're welcome, and thank you 🙂

Runs a bit in the family I think; I'm a teachers' son who somehow ended up doing mainly software development so far. (These skills are quite useful when writing documentation and reports.)
I'm trying to branch out a little for my own sake though, so who knows what the future holds.

I'd say my number one advice for explaining well is to avoid jargon and to be open-minded about which common ground to start with, then build from there without going into too much theoretical detail. (If anyone wants to explore more, they can follow those links, after all, but that shouldn't be necessary to see the main point.)

It's harder to do online than in person, since there's no live feedback and fewer clues where to start, but you can still take some shortcuts based on the context of the discussion.

That said, sorry for all those edit notifications 😅
I'm pretty typo-prone especially on my phone.