METABYTE
Back to articles

5 Types of Engineers I Met as a Technical Writer (and Lived to Tell)

Being a technical writer is like being a zoologist in the wild: you observe, classify, and try not to get bitten.

8 mai 20262 min read
5 Types of Engineers I Met as a Technical Writer (and Lived to Tell)

Working as a technical writer in an engineering world is like being the only person who brought documentation to a party where everyone else brought commits. Over the years, I've identified five archetypes that appear in every team. Grab your popcorn: it's going to be painful and hilarious.

1. The Silent Genius This guy writes code that works like a Swiss watch, but ask him how it works and you get monosyllables or grunts. Extracting a description from him is like trying to get the Wi-Fi password from your grandma: the signal is there, but nobody knows the password. You end up reading his commits and hoping he didn't use Hungarian notation.

2. The Enthusiast Architect He loves complex terms and patterns. Instead of "execute a request," he'll say "initiate an asynchronous call via the event bus." His documentation reads like IKEA instructions written in Elvish. But if you translate it, there's often a brilliant solution hidden inside.

3. The Always-Busy He has 47 tasks in JIRA, 5 open pull requests, and a meeting in 10 minutes. To your question, he replies, "Check the code, it's obvious." Spoiler: it's not. You have to ambush him at the coffee machine and pry the answer out between espresso sips.

4. The Perfectionist He'll fix a typo in a comment even if it breaks the CI. His pull requests are works of art, but the review takes longer than a overnight deploy. With him, documentation will be perfect, but it'll arrive sometime next decade.

5. The Soul of the Team This engineer knows all the memes, jokes about JavaScript frameworks, and is always ready to help. He's your lifesaver: explains complex stuff in simple words and even draws a diagram on a napkin. The only downside is he gets distracted too often and writes code less frequently than jokes.

METABYTE studio comment: We know all these types and a few of our own. If you need documentation that both juniors and team leads can understand, we'll translate from "engineer" to plain English. And yes, our coffee is top-notch too.

NEXT STEP

Liked the approach?

We apply the same principles to client projects: AI, automation, products that don't die after launch.