Software Engineers should be good writers
Expressing your work is crucial in being effective
At the start of my software engineering career, I focused more on writing good code, following best practices, learning new programming languages, and engaging in stereotypical new graduate activities.
Over the years, I have become much more seasoned in the industry. This includes changing my mindset and being more flexible in my thought process. I have entertained ideas that would be considered offputting right out of college. Software Engineers should focus on writing code. Right?
Software Engineers should be good writers. They should be great writers. If a tree falls in the forest and no one hears it fall, did it even fall? If a software engineer delivered a project and no one knew about it, did they even deliver it? The comparison is intentionally outrageous to draw attention to the point. You need to express yourself and talk about your achievements.
None of us should expect others to “just know” about our achievements. Do you know everyone’s achievements? Even if they somehow know about your achievements, do they have a proper picture, or is it a misrepresentation? When you expect others to know about your work, you are handing over the power of narrative. Seize it! You should control the narrative of your accomplishments.
If you know how to write well, you will be much more effective in communicating your ideas. Writing is more than just a bunch of words strung together. It’s a story. It should be compelling and hook the reader. It should be precise and express what you mean.
I strongly suggest reading William Zinsser’s book “On Writing Well” about the importance of writing well. It is a game-changer. When I compare my writing style today to two years ago, I can see a stark difference. I get to the point quickly. I strive to start with the punchline. I aim to embrace the letter and spirit of the book in the coming future.