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.
My career path is also moving towards doing more GUI work. I have a
Fine Arts/English background. In my previous position, I started off
creating icons for custom QNX apps (hello Bob). In my current position, I
started creating icons and icons sets but also had the opportunity to learn
and use some proprietary controls. I was soon assigned the task of
developing the interface for our paint program. I'm now doing GUI work on a
wide variety of projects which includes our flagship product.
In my experience, the documentation team needs to add skills to the
development process. Since I have been at Inscriber, the documentation team
has always had a good relationship with the development team. I just started
building on this relationship. I found that some developers are not as
interested in the often menial tasks of editing and maintaining resource
files (.rc and .res files in the Windows world). Once I took on this
responsibility for one project, developers saw me as a resource they could
use. Pulling a few late nights to update the entire GUI before a major trade
show doesn't hurt either.
Hope this helps. BTW, anyone going to User Interface 98 in Boston
next week? Drop me a line if you are.