TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> I’m editing a specification, and I was merrily redlining all sorts of
> convoluted wording to be simple and straight-forward.
It could have something to do with groups wanting to defer liability onto
another party. So when something bad happens each can blame the other for
not properly interpreting, or writing, the spec.
And most specs are temporary documents that are used to convince management
to build whatever is specified. Then all the work goes into the detailed
design documents and nobody refers to the spec again.