Manager of Technical Communications

I'm a hardware guy living in a software world, and have been part of the EDA industry almost since its inception. Over my career I've held a number of positions including design engineer, applications engineer, technical trainer, and technical writer.I've had the great fortune to work with a wide range of tools including schematic capture, PCB, and IC layout software, as well as digital simulation, hardware emulation, and formal verification. My current role in Technical Communications is to tell my company's story in various forms such as product manuals, App Notes, data sheets, and training.


's contributions
    • You're very welcome. I hope the template comes in handy. BTW, I revamped the presentation and turned it into a video. (I installed links in the comments above as well as on the front page of the Template Tour doc.) Interestingly, engineers are happy to spend time designing or coding, but hate to spend time documenting. But this is a critical task, especially if we want the product of our engineering efforts to find a wide audience. Hopefully, this template (and a few other things) can help folks along.

    • I remade the Template Tour presentation and turned it into a video. It runs about 6 minutes, and it expands a bit on how to use Styles in Word. It's on YouTube here: Or you can download your own copy (about 80 Meg)

    • Hi Aubrey. I can appreciate your sentiments regarding Word. If it's any consolation, you're in good company: over the years many people (far too many) have struggled to get Word to behave. This is unfortunate because in the largest of ways, Word is "the tool nobody knows they have". Interesting you should mention China. My current employer has a large staff in Shanghai, and all of their documents are produced in Word. (No surprise here - they all have a copy of Word, and they all have experience with it, albeit, missing a critical understanding of how Word really works.) I created an hour-long training for the staff, and everyone came away surprised about how Word works and what it can do. I’ve decided to publish my Word training presentation. (I'm tidying it up for public distribution.) It's not long, and should be a real eye-opener for lots of folks. In the meantime, I'm willing to help anyone that's struggling with a Word doc. Can't get your numbering to behave? Struggling with Headings and indents? Table of Contents won't auto-generate, or can't get your PDF Bookmarks to come out? Drop me a line and let's see if we can get your stuff all fixed up. (Folks living in Silicon Valley: we can sit down somewhere if you're willing to buy me a coffee.) I’m certain we can get your doc to work the way you want. The answer is right under your fingertips -- it's been there all along.

    • Glad someone was able to make this work. I tried to show this with a walk-through here: This is actually 7 foils; the walk-through starts on page 2.

    • Say, did anyone try my trick of setting up part of your copyright statement with "Date = yyyy". If you did, then your copyright came up automatically with the current year. E.g.: Copyright 2004-2017. Set this up in your docs (headers/footers, boilerplate pages, etc.) and you'll never have to manually edit this field again.

    • BTW, my first introduction to text-to-speech came from the program "Speakonia", free software that worked on Windows XP. ( The instructions recommended using the Microsoft voices, "Mary, Mike, & Sam". Speakonia is no longer supported, and doesn't work on Windows 7 or 10, so I switched to Ghost Clipboard Reader. (It uses different voices, but I still think of the female voice as "Mary".) For the Apple crowd, I believe Mac's have had text-to-speech built in for a while. Apparently thinking different meant thinking ahead. :-) -R.G.