Hi. I'm Robert.
I'm an independent technical writer in Chicago.
I write API documentation. I've been doing it for a long time, am good at it, and can help you.
But I'm a different kind of tech writer, combining multiple disciplines, new technologies, and a common sense approach to projects.
Let me help you on your next project. Write me at Robert@WriteOnce.org.
Places I'm speaking. |
Passwords really do work, and here's why. |
How to introduce Office automation to writing teams. |
Can you inspire innovation, or does brute force work? |
Listboxes and Datagridviews are excellent ways to present a lot of information. They can be extremely fast and versatile, too. |
Problems exporting Word to Flare can be exacerbated with all those Span tags. This takes care of that in one operation. |
Are you getting "Too Long File Names" errors? This is your fix. |
Don't give us a new version of Flare, just fix the bugs. |
Put search and replace on steriods and use this with Madcap Flare. This was my 2018 STC Summit presentation. |
We can get the tools, we just need to start seeing everything as being broken. |
Things you need to know but no one tells you. Except me. |
We're being oversold with API documentation generators. See why I think that. |
If that's it, then no thanks. We're better off on our own. |
Can clients get started with your APIs in fewer than 30 minutes? Perhaps not. |
Can Word Solve Its Own HTML Problem? You Betcha! |
It's easier than you think, but it takes planning. |
There is a method to all this. |
Some simple steps will help. |
C# has lists and dictionaries now. |
Supercharging find and replaces. |
Three Visual Studio projects as examples. |
Sometimes the best way of understanding something is to look at someone else's. |
In fact, you should use multiple style guides. |