technically speaking

No comments

In my day job, I write technical documentation. Well, that’s what the job description says anyway. A good chunk of what I actually do is editing, formatting and coding, and organizing information. To be fair, I get to do a decent amount of actual writing, especially when we’re getting ready to release new features.

I also spend a lot of time researching APIs, and documenting the attributes our software will be ingesting and making available (we’re a data technology company). Some weeks it feels like all I do is this part of the job.

Sometimes though, I get to wrap my hands around a nice juicy project like a complete docs redesign/reorganization. This week I am just wrapping up one of those. There is something so satisfying about pushing that Publish button at the end of something this large.

Of course, most of our users will never know the amount of work that goes into something like this, and only a few of my coworkers (mostly other writers) will get it either. But that’s okay. I don’t need recognition for these things. If I’ve done my job well, my reward comes in the form of no one reporting broken links or missing information.

I push that Publish button tomorrow on the last piece of this project tomorrow afternoon. I’ll have a little celebration on my own after, then I get to spend my weekend writing non-technical stuff again.

It’s not a bad way to live.

Photo by Luca Bravo on Unsplash

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s