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 wouldn't sweat it. It's a social site for a social community. I
think the way the problem was found, reported, and fixed (within 24
hours) was appropriate for such an environment.
On Mon, Sep 13, 2010 at 5:03 PM, TECHWR-L Administrator
<admin -at- techwr-l -dot- com> wrote:
>
> On Sep 13, 2010, at 12:48 PM, Richard Mateosian wrote:
>>
>> Fixing problems when you see them is good. Going live before testing changes
>> is the problem. ...RM
>>
>
>
> Well, in an ideal world, you'd be right. But the fact is,
> sometimes conditions don't allow for _exhaustive_ testing.
> If we were to try to exhaustively test, nothing would ever
> happen. And so it is, with TECHWR-L as well as any number of
> other things, that issues are found in the real world.
>
> But certainly in my world, where the sky is still blue,
> this probably won't be the last whoops to hit the site.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
LavaCon 2010 in San Diego Sept 29 - Oct 2 is now open for registration.
Use referral code TECHWR-L for $50 off conference tuition!
See program at: http://lavacon.org/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
