The Noob Tech Copywriter Diary: Entry 1, where I tell you how it all began.

Dear Diary,

This is my first entry. I’m writing to share my experience as a first-time tech copywriter. I’ll talk about the challenges I faced, cool stuff I got to do, and sleep-deprived developers I bugged with questions (pun not intended).

But first, here’s a bit about me. I have a degree in communications and I’m also getting an MA. I studied literature in high school, and some of my main hobbies are making videos, reading, writing fiction, and watching vlogs and TV shows. Despite my clear orientation towards the arts, I’ve actually taken some HTML and CSS courses, but aside from some basic HTML, when it comes to programming languages I’m as panicked and clueless as a deer in front of a laptop’s bright screen.

Dipping my toes into the tech sea

I was hit by new technical things on my very first day. I was lucky enough to catch the release of my company’s new website, and thus, I was given the task of testing it out, to make sure there were no issues (or bugs, as developers call them). It wasn’t so hard, and I think I did pretty well. I also discovered I pay attention to detail quite well.

But enough humble brags. Here’s what didn’t click that day - choosing articles about tech and writing texts about them for UPDIVISION’s social media pages. Understanding the articles I was reading was a major challenge in itself, let alone writing a small intro for each. I ended up spending a lot of time on this task, and it wasn’t great. I felt like I was pulling myself down with my lack of knowledge. Looking back, I should’ve asked for some help.

Catching more bugs and other code kritters

I spent the next few days writing for the company’s portfolio, new software made and launched. I was also given another unexpected task: testing several functions of a complex B2B ecomerce they were getting ready to finish. I thought it would be fun - and it was. I spent many hours on this, but it activated my OCD in a healthy way. I got to use an app called ClickUp (between you and me, it took me an hour just to figure out how to use it) where all the elements of the developing process were listed, including the bugs. As a longtime Sims player, I was already aware of the term “bug”, but I learned it’s a more broad term than I thought: for me, in The Sims, a bug is an endless loading screen, but things like random townie Sims dressed weird didn’t feel like a bug, but it most likely was. While testing, I couldn’t help but feel bad for nitpicking and naming small things bugs. And by small things, I mean stuff one would name “Not a big deal, sorry”.

The interesting thing about testing is how conflicted it made me feel: I know developers work hard, and a lot, and I felt like I was stacking more and more on top of the work they already had - the bugs I was finding had to be fixed, of course. But at the same time, I felt that I helped the users of the app by improving their experience. Moreover, maybe the developers wouldn’t have found that stuff. I might actually have OCD:)

Lost, but not the TV series

I spent the next few days doing a mixture of portfolio writing, UX design, and retesting, alternating between them all. And by that I mean, when I felt stuck and lacking info for one activity, I went to another, then went back to the first when I got the answers I needed. I slowly stopped feeling bad about constantly asking developers for help and explanations. After all, I couldn’t do my job without their help. By the way, if you guys are reading this, thank you. 

UX design was certainly interesting to get to try more of. My role in this has been minimal, so far, but making use of my prior experience with graphic design was nice. The program we use, called Figma, reminds me a lot of Photoshop. But UX design is totally different from what I’d done before. I realized a major part of it is figuring out how a user would navigate the pages we’re designing. At times it might seem tedious, but I always dig things that combine tech and creative arts. Not to mention I can focus on this while listening to my favorite songs, so that’s a bonus.

That wraps up my first week. It was certainly a new experience for me, as much of a cliche that is (after all… it’s the truth).

What I have learned 

• Testing can be fun
• Developers are incredible
• Don’t be afraid to ask for help
• Research! Research! Research!
• (Tech) Copywriting isn’t something you can learn in 10 minutes.

Tune in next week to hear more about my ups and downs as a copy noob. Spoiler alert: I wrote lots of things.

If you liked this article subscribe and get an email when we publish new, juicy stuff. We hate spammers, so we don’t spam.