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 don't see your argument. The two tasks are entirely different,
requiring different aptitudes. Writing isn't difficult; or at least not
to me. That's one of the reasons I am a TW, because I'm good at it.
I'm good at it because it comes fairly naturally. Programing is
different; it requires a different type of logic skill to understand
programming to the one writers use. (I'm hypothesising here.)
I don't 'get' program code in the same way that I 'get' front end
stuff. That's why I can write for end users, but can't write the code.
I find programming difficult, but the programmers I work with find
writing about it difficult. They're just different skills sets that
different people do.
Regards,
Ant
bbatorsk -at- nj -dot- devry -dot- edu wrote:
Brecht, I believe, talked about the simple that is hard to make. One
would assume, I thought, that technical writing was harder and more
exacting than programming. It takes more training to be a competent
technical writer than to be a good programmer.
I would like to set the qualities of good programming against the
qualities of good technical writing to see which simple is harder to
make.
