tag:blogger.com,1999:blog-7354171578524044422.post3193497046011584610..comments2008-12-16T08:08:56.206ZDavid Farbeyhttp://www.blogger.com/profile/01802930753043960426noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7354171578524044422.post-50947249081981860492008-12-16T08:08:00.000Z2008-12-16T08:08:00.000ZHello Anne,<BR/>Thanks for your question.<BR/>Tools like the one you describe are useful if documenting databases are the core of what you need to produce, and they serve the needs of your audience. They may have a secondary benefit in helping you understand the inner workings of the programme you are working on.<BR/>If you are producing documentation for non-technical users, you need to concentrate on their tasks, from their point of view - which is often far removed from the way things look to the database developer.David Farbeyhttp://www.blogger.com/profile/01802930753043960426noreply@blogger.comtag:blogger.com,1999:blog-7354171578524044422.post-31898457086246386032008-12-16T02:40:00.000Z2008-12-16T02:40:00.000ZI've recently decided to become a freelance technical writer, and your article caught my eye. To assist me with some of the mundane IT system documentation, I'm using documentation generators (e.g. Adivo's TechWriter for Databases http://www.adivo.com/techwriter-for-databases.aspx).<BR/>I'm very happy with the tool, and I think it's giving me a technical advantage over others because I can generate/update doc quickly and add my own annotations and additional content easily. But I wonder what your opinion is of such documentation generators and if you think they help or hinder the process of making better documentation??<BR/>Thanks for any advice.Annehttp://www.blogger.com/profile/00791960096725953639noreply@blogger.comtag:blogger.com,1999:blog-7354171578524044422.post-27356501251644533782008-06-19T04:44:00.000+01:002008-06-19T04:44:00.000+01:00Good article, thanks.Deanhttp://www.blogger.com/profile/06733436163457000051noreply@blogger.com