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 appreciate your thoughts. Very clear. Am not sure it
flies like that everywhere, though. Are you an
academician by any chance?
LOL! Kidding.
--- Goober Writer <gooberwriter -at- yahoo -dot- com> wrote:
>
> > Yeah, like having your supervisor say, "Why'd it
> > take you so long to learn how
> > to document that? You're being paid to write, so
> 80%
> > of your time should be
> > writing, not fiddling with the software.
> First, I don't smile and accept criticism like this.
Sometimes, you gotta.
> What this situation clearly denotes is your
> supervisor's inability to do his/her job, as any
> manager, to be effective, must know the what, why,
> and
> how of what their employees are doing. The manager
> doesn't need to know the details, but definitely a
> hefty gist of the job.
Sometimes, they want to know why you copied and pasted
*that* way.
>
> Second, I wonder if a lead programmer would be
> treated
> the same.
Maybe not. But, your not a lead programmer, are you?
And, the boss might not know C# but he certainly knows
how to "write."
> "You had 4 months to architect this
> component, yet 70% of your time was spent in
> meetings
> Third, I would reply and engage in constructive
> conflict. "I understand you are upset that I have
> spent so much time researching this project and
> little
> time (in comparrison) actually writing about it.
...
Do you really get to finish this? <lol!>
>
> Finally, this entire mindset of "work harder, not
> smarter" is the result of prolonged exposure to CRAP
> (Cursory Reliance upon Analytical Planning).
ROFL!
>
> Cleaning up CRAP boils down to a simple formula:
>
> proper planning + systematic approach = good process
>
In a perfect world ... sure.
Anyway, great post! Thanks for thinking of me. <g>
NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3
---
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.
