Hacker News Reader

Comment by jes | Hacker News Reader

Wasn't familiar with RACI acronym:

RACI is an acronym derived from the four key responsibilities most typically used: responsible, accountable, consulted, and informed. It is used for clarifying and defining roles and responsibilities in cross-functional or departmental projects and processes.

I wish more people briefly defined acronyms at first usage in a document.

View on HN

I agree, but it's a hard balance to strike and depends on the writer's target audience. RACI is a pretty common acronym for anyone doing project management professionally. I'd not define REST, HTTP, etc; in an engineering doc.

How hard is it to use <abbr title="...">?

Details can be hard, even if small. Don't get me wrong, I try to do it myself every time I write, but I often find myself wondering if it's worth to link to a definition or will it be too obvious and come across as condescending. Maybe is just me.

For me an author disqualifies if there is an unnecessary use of jargon. In my experience the use jargon is often just a distraction from the fact that there is no thorough understanding of the subject.

Whilst I don't think RACI is that uncommon speak. I do think that there should be a glossary if people are using a lot of acronyms.

Like another poster said, in an engineering doc they might not spell out what REST or HTTP stands for or means and that makes sense.

There are even other forms like RASCI (S for support role)

Reply on news.ycombinator.com