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've requested from our VP of Engineering that I get a week from
whenever the code freezes, and he agreed. So far, for each interim
release of our fledgling product, I haven't needed that whole week
because I've pretty much kept up with the changes along the way.
Now we're in final bug week for the 1.0 release to our first paying
customers, and the code is still changing. There's hardly "slush," much
less freeze, but I've still got my promise of a week after the last
change, in case I need it, which is a nice buffer for verifying
everything and generating final PDFs and help files.
