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've found that sentences so convoluted that they need to be diagrammed
usually contain factual errors once I parse them. If I can't understand
it
the engineer probably didn't either. Of course, I speak (and read)
fluent programmer.
----------
From: Rose Wilcox[SMTP:RWILC -at- FAST -dot- DOT -dot- STATE -dot- AZ -dot- US]
..
I haven't found it much use in actual
*writing*; however, I have used it occasionally to parse a sentence
written
by an engineer or programmer. Sometimes diagramming a particularly
obtuse
sentence has allowed me to discern what was meant, as opposed to what was
said.
