Post #3578429

2026-07-04 04:11 UTC

@mikalai@privacysafe.social @akareilly@hachyderm.io My personal go-to is that if I can't explain my jargon in terms a 10-year-old can understand, then I'm not communicating my field effectively to a layperson. I'm not equating a layperson with a 10yo; but if I haven't simplified my language appropriately, then I'm not meeting the other person where they are.

Replies (2)

@mikalai@privacysafe.social 2026-07-04 11:22

@courtcan@mastodon.social @akareilly@hachyderm.io This is the right approach, have also this top level of understanding, ... and done in UI be it GUI or cli (there are nuances). Let's step from me/mine for a moment. There is some dev, writes open source tool that covers full or some more of tech stack. He/she already covers few semantic layers. Let's ask from him/her to cover one more layer. At paid work it is called work. At hobby it is a burn out. What you say is my goal too. A star directing way.

Open ##3578428
@mikalai@privacysafe.social 2026-07-04 11:30

@courtcan@mastodon.social @akareilly@hachyderm.io With the original toot situation, lay person that doesn't know what is cli wouldn't find the tool in the first place. Was lay person an audience? Is open source developer attempting to expand audience? If lay person can't fond a tool, and demand for xyz comes from someone who evidently has found it, has showed "jumping endurance", then demand toward unpaid developer has this strange taste in developer's mouth. Note, in developer's perception, not the demander's one.

Open ##3578541