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.
We are by no means a typical shop. Our coders are either cowboys or ESLs,
each adhering to his/her own "process". They're coding with such tools as
VITK, MITK and Visual Studio, along with C++. Their manager is only the
manager through default (read: attrition) and comes from the medical
imaging research world, as do many making of his team. If anything is to be
done in regard to laying out a new formalized process, it appears I'll be
driving the effort through said manager. If left on his own, he's so
short-handed that it'll just never happen.
I don't know what an IDE is (except that it used to be a hard disk
interface in the olden days).
On Mon, Nov 12, 2012 at 10:09 AM, Robert Lauriston <robert -at- lauriston -dot- com>wrote:
> What do they code with? IDEs typically have those tools.
> If you want a GUI tool:
> On Mon, Nov 12, 2012 at 9:34 AM, Chris Morton <salt -dot- morton -at- gmail -dot- com>
> > My associates are good coders (as far as I know), but designers and
> > grammarians they're not—especially when it comes to the ESL folks. We end
> > up wasting a lot of time and effort with their "code first, design later"
> > mentality, which invariably delays user manual additions and SW delivery
> > dates as we massage iteration after iteration of the UI. I'm wanting to
> > proactive and suggest a procedure whereby a written GUI spec, complete
> > proposed screenshot(s), needs prior managerial approval *before* any
> > begins. Along with this the coder would have to submit an electronic copy
> > of screenshot to me, so I have a head start on shoehorning it into the
> > pre-existing user manual.
> > So, any tips on easy-to-use GUI mockup software for coders?
> Writer Tip: Create 10 different outputs with Doc-To-Help -- including
> Mobile and EPUB.
> Read all about them: http://bit.ly/doc-to-help-10-outputs
> You are currently subscribed to TECHWR-L as salt -dot- morton -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
Writer Tip: Create 10 different outputs with Doc-To-Help -- including Mobile and EPUB.