4 ms·
A glossary is the most important document ANY project should have and maintain. Everything else is secondary.
by HeavyStorm 3y ago
A glossary is the most important document ANY project should have and maintain. Everything else is secondary.
- drittich 3y agoPlease explain what ANY expands to...
- lawn 3y agoNah, it doesn't pass the sniff test. Is it more important than a list of critical bugs? A document explaining how a developer can get the application up and running? A document detailing how the production server is setup and how to gain access? When you think about it, lots and lots of projects manage without any kind of glossary but would go up in flames without some kinds of documents.
- mike-the-mikado 3y agoPerhaps in terms of the importance to effort ratio. How long does it really take to maintain an adequate glossary?
- liamwire 3y agoAgree strongly. I think an even more insidious version of the parent comment is when common nouns that have specific meaning in a given context are used as such, without it being explicitly called out.
- hcarvalhoalves 3y agoAgree. A glossary is a way to introduce a domain piecemeal, without a long-form explanation.
- nuancebydefault 3y agoI find glossaries quite often not very useful because they tend to get copy/pasted across documents and the acronyms are often just expanded without giving the correct meaning in the context of that document. I'd rather have it fully spelled at first usage, with the acronym in brackets. This enforces a more natural order of writing and reading the document and provides a better context.