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.
1) Probably, I post twice per day to Techwr-l. Probably 5 minutes per
post. Actually, I probably post and/or read an hours' worth per day, or
five hours per week, including HATT, Framers, U2U, and WWP-Users.
2) These are included in my 60-hour total.
3) I work through lunch. That is, I eat a sandwich and keep working. I
did not include this in my 60 hour total. Let's say my efficiency is
50%. Thus, I work an extra 1/2 hour per day or two-and-a-half hours per
week.
5) Additionally, I do benefit from cruising the lists. My company
benefits, too. I saved a tonne of hours, and also some tech support
money, on my last project. I cannot quantify that, but one issue that
was resolved on WWP-Users probably saved me 24 hours of my time, for
maybe 15-minutes-worth of posting. Another issue resolved on Framers
probably saved me a couple of hours, for one 5-minute post.
6) If I am this busy, why write messages? To break up my day. For my
sanity. I have no tech writers here to bounce ideas off or to chat with
about my profession. The lists help me with these things. I do learn
some things from the list that I work into my products. If I had other
tech writers here, I'd probably post less. As a one-man-band, getting
fresh perspective and addressing long-term errors is difficult.
Additionally, my one request for tech-writing training this year (the
FrameUsers conference) has been turned down; so the lists double as
professional training for me.
7) I am that busy. I am expected to be here only 40 hours.
I am not offended by Bruce's post; I think it appropriate. I am very
curious to know what you all think of my response--on-list is fine, even
if you think me the most evil of slackers ;?).
-----Original Message-----
From: Bruce Wolf [mailto:bwolf -at- scheidt-bachmann-usa -dot- com]
Sean:
I didn't post this to the list because I don't want to appear to be a
smartass when I have a few serious questions. Feel free to quote the
questions to the list if you chose to answer there.
How many messages to TECHWR-L did you compose on company time?
Are these messages included in your 60 hour total?
If you are that busy at work, why write messages to TECHWR-L?
If you aren't busy, are you simply expected to be at work that many
hours?
November 2001 through the beginning of June 2002, I worked an average of
60 hours per week. This is considered the norm--perhaps even light--at
my organization; it is the culture. There is no increase in salary to
cover the extra hours.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Buy RoboHelp Deluxe starting at only $798: you'll get RoboDemo, the hot new
software demonstration tool that's taking the Help authoring world by storm,
together with RoboHelp Office. Learn more at http://www.ehelp.com/techwr-l
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
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.
