Who am I?
I’m Steve Arrants, a technical writer, an editor, and a documentation engineer. A documentation engineer helps companies find the most efficient way of creating, managing, and distributing their documentation. This involves looking at the existing systems and processes, and engaging with the doc team, management, and other stakeholders to find a good solution.
My background
I started out as a technical writer and took on more responsibilities and skills as an editor and then a documentation engineer. I enjoy working with teams to rejigger and improve their workflows.
I’ve been using MadCap Flare as an authoring tool for most of my career. But I’ve also used Markdown and a Docs as Code workflow, which I find works very well when documenting APIs and iPaaS and SaaS platforms. Docs as Code doesn’t require developers and engineers to learn new tools to write and review, or an investment in proprietary software.
Where I’ve worked
As a writer and editor I have more than twenty years experience in small and large corporate organizations in scientific and medical instrumentation, scientific journal tools, and other markets.
As a documentation engineer I’ve helped the organizations I’ve worked for improve their processes, become more efficient, and get the docs done faster and with fewer hassles. I’ve seen a lot of documentation problems in my career and have found ways to fix them.
Personality?
Here are the results of a personality test I took as a work exercise. People I’ve worked with tell me it’s accurate. I’m friendly and easy to work with, and I can take time to listen to your needs and help you find a solution.
Spare time and interests
I’ve been a Boxer dog rescue/fosterer most of my adult life. They’re amazing, loving, goofy dogs.
I spend time with my two at dog parks and walking some of Vermont forests and parks, with Graton State Forest as a favorite spot.