If you can write code, you can write a book. Here’s why.

We often split society into the ‘left-brained’ and ‘right-brained’. We are either logical, good at maths, destined for STEM, or, artistic, good with words, and led to creative fields. Once you’re put on one path, you’re told it’s impossible to step into the other. In reality, every person has both the creative and logical minds. If you are capable of complex maths, you are capable of complex creativity. With a shift in perspective, skill parallels like pattern recognition, spatial reasoning, and attention to detail quickly come to light.

So why does it feel so difficult to consider moving from a Tech Career to a Creative field?

STEM careers tend to be run by rules and grading. There is a right and wrong answer, something either works or it doesn’t. Your tests pass or they fail. It is easy to transfer the same approach to writing. If you’re not a good writer, you must be a bad one. Spelling and grammar must be correct. Your writing must have an innate and specific purpose. You must be qualified to begin. Many people dream of completing a creative endeavor, whether that’s a book or starting a blog, but they stop themself at the fear of failing.

Here’s the challenge news: There are no right and wrongs with writing. You cannot be ‘provably’ good enough to start. The only thing standing in your way is yourself. Who would you be if you allowed yourself to step out of the comfort zone of right and wrong, and instead embraced the unknown? What would you do? And how might it feel? On the outside, tech might seem as far from creative writing as possible, but I’m here to argue the opposite – knowing how to code isn’t a barrier to creativity, but, in fact, a major advantage.

Let’s break it down. Coding at its core consists of taking a theoretical idea and finding a way to use your keyboard to convert it into reality.

As a software engineer, you’re trained to analyze a problem and use logic to find an efficient solution within whatever systems and environments already in place. Your tool? Coding language.

Writing is not as different as you might think.

The Theoretical Idea: Your writing project, e.g. a book.

The Tool: The written word.

The Logic Task: How to arrange words, phrases, and punctuation to convert the idea into reality.

If Code represents a pattern of electrical signals in a computer’s memory or storage, Writing represents a train of thought in one’s own brain. Reading someone’s words gives an immediate and direct insight into their mind by recreating the thought, idea, or sentiment in your own.

As a writer, you are therefore faced with the challenge of how to use language best to recreate your thoughts to achieve an intended impact. What order of characters is needed to create as little loss as possible when converting an idea from the mind to the page?

A similar process can already be found in the soft skills needed to be a software engineer: Communication and Collaboration. Consider the way you communicate ideas to team members in meetings and presentations. I am certain you know how to creatively use language to hit an intended understanding. The process is the same. The only difference? The content.

No matter how familiar you are with writing, whether you’re a published author or a total beginner, starting a new written project can be daunting. Staring at that blank page and imagining the work ahead to turn it into a book, blog, or even personal journal, can be almost unbearable and there is something innately uncomfortable with being face-to-face with our own words. First-time writers can read tips on how to get started here, ’Can Anyone Write?’ but the tldr is that writing is an intimidating experience and, for most, it’s difficult to find the confidence and motivation to get started. My advice? Commit to the idea that writing is a process that you already know. Treat it the way you treat code.

The Writing Process:

1. Research → Read books and essays that inspire you, explore themes, and decide what you want your final piece to say.
2. Plan your approach → Make an outline, split it into parts, and create a writing schedule.
3. Set aside time to write and set yourself up as if you are going to code → e.g. same desk, headphones, lo-fi playlist.
4. Test your work → Read it. Does it feel right? Have you hit your intended goals?
5. Peer assessment → The really scary part. Send it to someone else to read and get their thoughts.

You know these steps. You know this process. You know you can do this.

All that’s left is to give yourself the permission to try. Can you step into a reality where logic doesn’t halt creativity? Will you accept the benefits of your STEM background in approaching writing projects? Do you agree that if you can write code, you can write a book?

The only way to truly know is to try. Are you ready to take that first step?