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.
Code first specs later (was RE: Release notes: term for bugs)
Subject:Code first specs later (was RE: Release notes: term for bugs) From:David Farbey <David -dot- Farbey -at- lazysoft -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 13 Jun 2002 10:45:42 +0100
Sean Hower wrote:
>>Johnathon West wrote:
>>In some small shops, it is only as they write the code that they
*discover* how they want it
>>to work. The design follows the writing of the code, not the other way
around....There was
>>*nothing* in the entire place written down as to what the product was
meant to do.
>--------------------------------------
>You're the third person, aside from myself, who has mentioned working in a
place that operated
>like that. I'm wondering how many places out there are like this. I wonder
how many of us on
>techwhirl have worked at a place like that.....maybe a poll could find
out...?
I am working at a place like that right now. I have been here for nearly
three years and it has been very exciting to watch the product grow and
develop. We now have reached a stage where bits of proposed functionality
are described in brief documents, and then discussed by everyone before they
are coded. But there was no overall spec before we started, although our
founder/CEO created a thorough theoretical description of what the product
was supposed to do. It is still pretty difficult for the QA people to know
what to test, and for me to know what to write in the User's Guide.
Check the Web site below for a description of what we have come up with so
far!
David Farbey mailto:david -dot- farbey -at- lazysoft -dot- com
Technical Writer
Lazy Software Ltd., UK http://www.lazysoft.com
Phone: 01628-642314
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
Check out RoboDemo for tutorials! It makes creating full-motion software
demonstrations and other onscreen support materials easy and intuitive.
Need RoboHelp? Save $100 on RoboHelp Office in May with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l
---
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.
