Technical Writing Summary - Barry Rogoff

Barry Rogoff 603-494-5874
Go to content

Main menu:

Technical Writing
Technical Writing Summary
Unlike most software technical writers I required minimal support from developers. I tested every aspect of a software product and often found more bugs than the QA department. I was able to read the code in the source code control system and write example programs that worked. The first database-related example program I wrote at Digital Equipment Corp. (SQL Services) was so good the product manager wanted to charge customers for it.

I also performed many critical support roles such as website development, release engineering, beta test administration, database design and implementation, configuration management, quality assurance, internal technical support, customer support, and classroom instruction. I worked for several startup companies that required extremely long hours and personal commitment in return for stock options.

The technical writing samples presented here are in reverse chronological order. Samples written prior to 2001 are not included. These samples are still technically Company Confidential. I have made them available for evaluation purposes only. By reading them you agree not to share them outside this context.

I had completed half of the Master of Arts program in Software Design and Analysis at Boston University's Metropolitan College when project pressure from Digital Equipment's panic-driven attempt to build personal computers made it impossible to continue.

The eDialog and Vertica writing samples were created in Author-it, a highly-advanced authoring/publishing solution similar to Madcap Flare.
Welcome | Customer Support | Technical Writing | Duplicate Bridge | Dell XPS-15 Laptops | Technical Services | Photography | General Site Map
Back to content | Back to main menu