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 am lucky in my situation because the developer who started our GUI was the
first to admit he couldn't write. He would frequently ask me what to write.
No discussion - just tell him what to write. Even though he is now gone,
I've tried to carry that attitude forward and most of the developers here
appreciate the help.
As for your questions about reasonable limitations, I have two cents for
what it's worth. We had a situation once where a check box was necessary
but even for a simple yes/no choice, the reason for making this selection
was complex and a description was even more difficult. We made the check
box description as concise as possible and then altered the GUI to fit the
lengthy description. If you set limitations, make sure they are flexible
enough to handle the exceptions.
Hope this helps
kholscher -at- nsisw -dot- com