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 think that curiosity, open-mindedness and a synthetic mind are the most
useful qualities for a tech writer.
Personnally speaking, I have studied science (Biology, Physics and Maths)
until two years after my A-levels. Then I switched to studying English (4
years). I started working as a teacher, quit, and started a DESS (MA
equivalent, maybe an extra year of study) in technical writing (1,5 years).
Since this diploma (2 years ago), I have begun studying technology (now
electronics, before, optics and mechanics).
Science has given me the rigor needed to approach difficult subjects, and
the efficiency to synthesise ideas and abstract concepts.
English has given me the command of the language and the curiosity to
understand how to use my mother language (French) better.
Technology has given me a practical and logical mind that is invaluable when
asking questions to engineers.
Ah, and theater practice has given me the confidence to talk up to people
and treat other workers as equals. (Though my parents claim that some kind
of family trait surely had an influence in this.)
We're not too far (in the spirit) from what Bonnie Granat reminded us "that
the seven liberal arts are: Grammar, Rhetoric, Logic, Arithmetic, Geometry,
Music, and Astronomy."
What has helped me most is that I am a grammar freak, and always thumb
through dictionaries and books about grammar and sentence construction.
Grammar requires a pretty scientific turn of mind, and is taught appallingly
in school, and possibly worse at university. Not taught at all in
engineering curriculum (as far as France is concerned). Most engineers I
work with (or am friend with) have two sides : Dr Jekyll designs the stuff,
Mr Hide writes their doc.
So I am absolutely convinced that technical writing should have a curriculum
of its own.
Amenagements could be :
1/ If a minor (in any other subject) studies, it should explain people how
to prepare information to facilitate the transmission of information from
them to the technical writer (or to themselves later on, since I had
numerous interviews where SMEs would ask "Did I really write this ? What do
you think I meant ? - Well, that was my question.)
2/ If a major, it should include a variety of subjects (grammar, visual
arts, communication skills, language exercises, numerous real-life projects,
teaching experience...), with minors in the subjects students are most
interested in at the time of their studies (chemistry, opto-electronics,
accountancy, object-oriented developement...).
I did usability, and enjoyed it a lot. I also did localisation, and hated
it.
Obviously, these suggestions are not concerned with funding at all...
Well, that was the un-requested for opinion of a young tech writer on what
lead her to where she is today.
Solena Le Moigne
Rédactrice Technique
Thales Communications - Cholet
solena -dot- lemoigne -at- fr -dot- thalesgroup -dot- com
I'm on DIGEST, reply directly.
RoboHelp Studio maximizes your Help authoring power by combining
RoboHelp Office and RoboDemo, so you can easily create professional
Help systems that feature interactive tutorials and demos.
---
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.
