---
title: What do I want to be when I grow up?
date: 2023-05-04T00:57:15Z
modified: 2026-11-10T03:01:40Z
permalink: "https://rrchapman.us/uncategorized/what-do-i-want-to-be-when-i-grow-up/"
type: post
status: publish
excerpt: "I promise you that, when I was growing up, being a technical communicator was not on my list of things to do. "
wpid: 894
categories:
  - Uncategorized
featured_image: /wp-content/uploads/2023/04/h2g2-definition-technical-writing-1.jpg
featured_image_alt: Technical writing is the art, craft, practice, or problem of translating that which is logical into that which is grammatical. Technical writing forms a bridge between the logical (the primarily binary concepts understood by computers, robots, lawyers) and the illogical (the haphazard, inconsistent concepts misunderstood carbon-based life forms, highly intelligent computers, lawyers) via the medium of the grammatical, the haphazardly logical system incomprehensible to both. The practice of technical writing presupposes that you, the illogical, actually want to learn about the logical subject, which of course is in all cases false. This basis in a false presupposition makes technical writing a pursuit typically favoured by those with arts degrees from obscure universities.
author: Robert Chapman
timestamp: 2026-11-10T03:01:40Z
tags:
  - Uncategorized
---

I promise you that, when I was growing up, being a technical communicator was not on my list of things to do. It wasn’t even on the list when I did my first technical writing contract.

A recruiter at Kelly Services needed a technical writer for a Boeing assignment in 1990. She didnʻt have one. She looked at my background, and decided I could do it. “Youʻll be great.” I believed her.

I wish I could thank her today.

## How did you become a successful technical communicator?

Somebody asked me how I became a successful technical communicator on LinkedIn. I had never given it much thought; it is something I simply do.

Wanting to be helpful, I thought about it a moment. From my phone, I texted back this answer:

> There isn’t one answer that works for all.
> 
> I love language and am fascinated with the details. Parallel construction. Active versus passive. Vocabulary.
> 
> I have a technical background that works well with computers and software. There are many types of writers requiring different domain knowledge. I can’t work in the medical equipment field as I donʻt have domain knowledge in that area.
> 
> I’ve been a high school teacher. That gave me domain knowledge into how people learn. I apply that frequently.
> 
> Can you tell a story? Can you think like the person who will want to read your work?
> 
> While technical writing is very formulaic, you need to draw upon your love of language to make it interesting enough. No one will read deadly boring content.
> 
> Keep reading and learning about the science and art of technical communications, and your domain subject expertise.
> 
> That is a quick summary.

This is the unadulterated answer, save for adding a “donʻt” where I missed it in the original. Also being an editor, there are a few things I want to reword. However, I wrote for the reader in a text medium, and she understood. Mission accomplished. My trait to want to be perfect can just be quiet for a moment.

Here is some elaboration on how I became a successful technical communicator.

## There isn’t one answer that works for all.

Iʻll admit being lucky I found this profession. I wasnʻt looking for it. I was looking for a job as I was approaching a time of crisis in my life.

There was no “technical communications” coursework for me, no certificates, no apprenticeship. I would not recommend this to others, although it worked for me.

Remember that I had basic written communication skills before my first gig. Since then, I keep learning about my profession. Things change. Never stop learning.

![It is de boer allike folle, 
oft de kou skyt of de bolle.
](https://i0.wp.com/www.rrchapman.us/wp-content/uploads/2023/05/It-is-de-boer-allike-folle-oft-de-kou-skyt-of-de-bolle.jpg?resize=525%2C525&ssl=1 "It is de boer allike folle,  oft de kou skyt of de bolle.")It is de boer allike folle, oft de kou skyt of de bolle.## Fascination with language

Long ago and far away an electrical engineering major decided he really wasn’t an engineer and, after 90 semester hours, switched to being a history major in a Bachelor of Arts program. That person was me.

History was my second love. My first love may have actually been Physics, but I was thinking practically when I graduated from high school. “Be an engineer!” Seventeen year old males should not be practical. One will evolve after seeing things in college they had never imagined.

However, my second love introduced me to language and communications in all its glory. Reading. Writing. Humanities classes (the same I could have had as a Physics major). I even voluntarily took a course called “History and Structure of the English Language.”

As an interesting side note, having that linguistics course (History and Structure) put me in good stead the first time I met my late mother-in-law. She was from Friesland. West Frisian, her first language, is the closest language to English. She had several plates on her wall with sayings in Frysk and Nederlands. There is one a tried to translate, based on what I had learned in the linguistics class:

> It is de boer allike folle,
> oft de kou skyt of de bolle.

I was getting close (but not quite making it). She saw what I was doing. She translated it for me:

> To the farmer it is alike
> whether the cow shits or the bull.

Of course I laughed. I think that was the moment she decided she was going to like me. And, I learned that the more literal translation of the verb used for defecation is not as forbidden in Frisian as in English.

> Brea, bûter en griene tsiis is goed Ingelsk en goed Frysk. 
> Bread, butter and green cheese is good English and good Fries \[Frisian\].

I was sidetracked from learning some Scots Gàidhlig after my parents moved here from Missouri. In the past few years, I’ve gained a fascination with ʻŌlelo Hawaiʻi. (To be honest, I’ve gained fascination with anything Hawaiian.)

### Addendum

Why did I stay at what is an institution of science and engineering when I switched majors to History?

That answer is best answered by Mohammad Dehghani, PhD, Chancellor of the MIssouri University of Science and Technology. His Friday email on the week after I wrote this blog piece answers that question: [To the End of the Earth!](https://chancellor.mst.edu/emails/2023emails/05-05-2023/)

For the record, [Dr. Jack Ridley](https://150.mst.edu/stories/audio-interviews/jack-ridley-audio-interview/) was my academic advisor as a History major. I survived Historiography (with its dreaded scavenger hunt in the library) with [Dr. Wayne Bledsoe](https://news.stlpublicradio.org/other/2017-08-22/bledsoe-to-host-last-broadcast-of-bluegrass-for-a-saturday-night).

## Technical background

Did I mention I was originally an electrical engineering major in college?

Did I mention I was an official tutor for the second semester Keller-plan phyics classes in college?

Did I mention my 25 semester hours in mathematics?

Did I mention that I’ve been a technical communicator for over 30 years?

When engineers and other technical experts start describing something, I can usually follow along. I know when to ask questions. I know when I need to clarify what I think I heard. Having technical coursework and years of experience helps me to translate engineering to English.

I still don’t like thermodynamics, though. I may be a nerd, but I am not a mechanical engineer.

## Being a teacher

Since I paid attention in class, I know Bloomʻs Taxonomy of Educational Objectives and Piaget stages. I know to tell them what you are going to tell them, tell them, and tell them what you told them.

Most importantly, I learned you don’t learn what is expected. You learn what is inspected.

When I created web-based courses, I also learned that adult learners are not “formal operational learners” when they are at work. Adult learners are very much “concrete operational” when at work. They don’t want theory; they want to do their job. Forget that to your peril.

There are times that I miss being in a classroom, though. Nothing felt as good as the time I was a substitute teacher for a combined K-1-2 class (rural school). The first grade students figured out how to use their phonics lessons to sound out words they didn’t know in their reading lesson, with some encouragement from me. “You can do it.” They believed me.

![Fractured Fairy Tales](https://i0.wp.com/www.rrchapman.us/wp-content/uploads/2023/05/Fractured-Fairy-Tales.jpg?resize=525%2C350&ssl=1)

Fractured Fairy Tales## Telling a story

Growing up, many of us learned to be truthful by hearing a story about George Washington not telling a lie about chopping down a cherry tree. We also learned from Aesop’s fables and Grimm fairy tales. Well, maybe _Fractured Fairy Tales_ during _Rocky and Bullwinkle_. However, they were stories

Stories work for adults, too. “[Frodo lives](https://www.americanforests.org/article/the-ent-activist-why-the-lord-of-the-rings-became-a-counterculture-icon/)” was a call for environmental action in the 1960s and 1970s. (If you have only seen the movies and not read the books, you won’t get how the _Lord of the Rings_ trilogy can do that.)

As I have said earlier, technical communications can be formulaic. There are simple, effective ways to tell someone [how to interact with a web page](https://learn.microsoft.com/en-us/style-guide/welcome/). When giving a series of steps to complete an action, don’t confuse your readers by straying from verbs like select, enter, scroll, and drag. If you use “choose” instead of “select,” your readers will wonder if these are different actions. Long paragraphs do not scan easily. Keep it simple, essayist.

However, you can employ good communication techniques to generate enough interest to keep people reading. Tell the story of a journey—an epic journey—to accomplish something. Keep it familiar but remember that material to be localized in another language can’t depart from basic structure. You will have to include your steps, numbered from “1” up to “10,” but you’ve built excitement for the journey.

Do I always accomplish that as a technical communicator? Unfortunately, not. But I try every time.

## Keep learning

I figured out how to use Microsoft Word—the non-Windows version–for creating my first technical documents while at Boeing. Do you know what a “side by side paragraph” is? (It is how you created a table before tables.)

Since then, I’ve mastered Adobe Captivate, analyzed data with Microsoft Excel, and created structured documents using the Syncro Soft Oxygen XML Editor. I didn’t do that by _not_ keeping up with my profession.

For that matter, I wasn’t afraid when I got a call to work an assignment when someone walked out that morning because of a new word processing program; WordPerfect for Windows had just come out. Then there was that time I was an editor at Microsoft when a group was using Author-it to prepare text for localization. Don’t be fearful.

There was a time when style guides said that you didn’t use a bulleted list unless you had at least three items for the list. Now, web usability calls for making things scannable with consistency, so you might justify even a single item in a bulleted list to maintain parallel construction. What works changes; keep up.

## A fun challenge

I still enjoy the challenge of telling or instructing others as effectively and simply as possible. So, I’ll keep being a technical communicator! [After all, I have an Arts degree from an obscure university](https://www.h2g2.com/entry/A425431).