Conversation

Notices

1. Adrian Cochrane (alcinnz@floss.social)'s status on Friday, 17-Feb-2023 03:03:12 JST Adrian Cochrane

   In much of the advocacy for "plain English" writing, the only real disagreement I have is the opposition to jargon.

   I get the impression this is mostly coming from managers who dislike their own jargon & probably have good reason for it. In my & many other fields, given the right audience, jargon helps a heap with clarity & concision! Isn't that the point of Plain English?

   Well, when writing hypertext I can link to definitions...

   Don't know why this came back to my mind today.

   • Michael Downey 🇺🇳 (downey@floss.social)'s status on Friday, 17-Feb-2023 03:05:02 JST Michael Downey 🇺🇳

     in reply to

     @alcinnz 💯 I think there's a time and place for jargon, but it should be documented, discoverable, and learnable, especially for people new to that field.

   • Tinker ☀️ (tinker@infosec.exchange)'s status on Friday, 17-Feb-2023 04:19:00 JST Tinker ☀️

     in reply to

     @alcinnz - Fully agree. Jargon is absolutely needed for those niche audiences that understand that jargon. Generalized language or "plain english" is absolutely needed for those general audiences whose experience or expertise falls outside of those niche groups that use the jargon.

     For mixed audiences, I use jargon, followed by a quick generalized definition, where appropriate.

     Adrian Cochrane repeated this.
   • Abandoned (doctormo@fosstodon.org)'s status on Friday, 17-Feb-2023 05:54:22 JST Abandoned

     in reply to

     • Tinker ☀️

     @tinker @alcinnz

     Wide words and deep words.

     Adrian Cochrane repeated this.
   • Tinker ☀️ (tinker@infosec.exchange)'s status on Friday, 17-Feb-2023 05:54:27 JST Tinker ☀️

     in reply to

     • Abandoned

     @doctormo - Oh, I like that. Thank you for sharing that!

     @alcinnz