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.
At 01:25 PM 7/3/01 -0700, John Posada basically asked for recommended
programming language(s) to should learn to strengthen his position in the
job market. Susan Gallagher subsequently wrote what I consider one of the
better responses along the lines of languages or scripting languages because
she related her comments that to requirements of the work environment.
May I question the underlying premise that the techwriter should learn a
programming language?
I do think an understanding of the object-oriented programming approach is
useful in most shops. And I second Susan's recommendation of Bruce Eckel's
books (on C++, Java, patterns). Eckel's works are more than compendiums of
how to do something. He encourages thinking and real understanding.
Nonetheless, after the introductory material on object-oriented programming,
the material may be more fun than useful for the TECHWR-L group.
Are we applying for--and most equipped for--programming positions or
technical communications positions?
Surely, do know what tool set/language is employed in our firm or find out
what is used in the industry in which we seek a position. Do learn enough
of that tool to be able to understand what code is doing.
Learn one of the languages for other than a hobby? If we invest that much
time and effort, we are likely to be disappointed to think anyone hires
writers or analysts for their ability to write code.
At least for those of us employed or seeking employment in a software
development house, allow me to suggest that we learn use cases, and then
move on to the larger topic of the Universal Modeling Language (UML)
graphical tool. We will then be able to review requirements and design
documents written with use case and utilizing UML use case diagrams.
Indeed, I suspect that we are more likely to be valued for our ability to
interview programmers and create use case documentation than to be valued
for our knowledge of x brand scripting idiom. Those lucky enough to have
access to Rational Rose (Rational offers CD and on-line demos) and a
computer that can run it should consider learning how to use it AFTER
reading up on use cases and, more generally, UML.
Alistair Cockburn's Writing Effective Uses Cases is one good place to start.
That said, I find Java programming to be mentally enjoyable. Without a M.S.
in Computer Science and 2+ years gainfully employed as a Java programmer,
the market is not very inviting for newbies. And right now I'm enjoying
having past my first year as a business analyst/technical writer.
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
TECH*COMM 2001 Conference, July 15-18 in Washington, DC
The Help Technology Conference, August 21-24 in Boston, MA
Details and online registration at http://www.SolutionsEvents.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
