Imagine a bacon-wrapped Ferrari. Still not better than our free technical reports.

Become a Better Developer: 3 Ways Writing Will Expand Your Mind, Improve Your Code and Grow Your Career

A long time ago, in a single-window basement far, far away…

Since the dawn of time, content marketers like me have been trying to think up clever ways of convincing programmers to write code a little less, and write more about the craft itself in technical blogs, articles, how-tos, reports and the like.

I’d love to tell you that it’s easy, but there is a perception of writing in the development community that isn’t always positive. Recently, I asked our Estonian development team what I could do to encourage them to feel like writing more…and here are some things I heard:

  1. I have no time to write, I need to pay attention to bugs.
  2. What, like technical documentation? Bleh.
  3. I don’t have anything interesting to say.
  4. Can I have my keyboard back now?

I remember hearing that developers like to be convinced by logic and argumentation, so I came up with 3 reasons why developers should spend some hours each week reflecting on their lives, work and thoughts as engineers of the virtual environs. I’m even willing to bet that your manager would look positively on these points below as well. Unless they suck.

Reason #1: Writing improves your mind and thought process

Whatcha thinkin’ about? Our thoughts are often a messy tangle of abstraction. I declare that writing out your thoughts and putting everything down “on paper” solidifies their existence and lets your creation come into being. Writing something down requires that your abstract thoughts not only become concrete, but forces you to think your problem-space through. Thoroughly.

It also means that you have to translate from your incomprehensible internal brain language into English, Russian, Portuguese or Chinese, and explain things using efficient and common language (or else your writing is unreadable). The idea is that this entire process exercises different areas of your brain. Now, I’m no scientist, but I think this article gives some good info about how creative thought, generally, works chemically. This is my favorite line, although what I comprehend from it is that creative people secrete some kind of brain chemicals that makes their thinking awesome:

Why Devs Should Write More

‘[Highly] creative individuals “may be endowed with brains that are capable of storing extensive specialized knowledge in their temporoparietal cortex, be capable of frontal mediated divergent thinking, and have a special ability to modulate the frontal lobe-locus coeruleus (norepinephrine) system, such that during creative innovation cerebral levels of norepinephrine diminish, leading to the discovery of novel orderly relationships.”‘

Reason #2: Writing improves your code and daily work

Are you suggesting the writing code isn’t creative? Uh, no. In fact, quite the opposite. Being a good coder requires creative skills and talent beyond working with the implied rules of the programming language. Coding is an art form and spending time refactoring or reflecting on that pesky bug, for example, lets you attack challenges in different ways later on. A developer named John Hawksley recently expressed a desire to write more, but was unsure of how it would fit into his workweek (I offered to call his manager, by the way, and I’ll call yours too if you want):

Why Devs Should Write More Twitter Conversation

When trying to learn new tools, technologies or processes, writing a tutorial or how-to in a friendly, welcoming way isn’t an easy task, but teaching it to someone else is one of the best ways to learn it well. If documentation is part of your job, writing about your code can help you complete those less-desirable task painlessly & efficiently.

Being able to explain complex concepts in simple ways teaches you many skills, but first among them is how to write readable and maintainable code. Teams often do post-mortems when code breaks or bugs are shipped with a release, so why not apply the same level of reflection and analysis on your own work? Ideally, before something goes wrong ;-)

Reason #3: Writing improves your network, profile & career opportunities

Who are the most well-known people in the JVM-based software industry? Many of the most successful people that I’ve met over the years–WARNING, NAME-DROPPING COMMENCING: Martijn Verburg, Ben Evans, Antonio Goncalves, Ed Burns, Bruno Souza, Michael Hunger, Lincoln Baxter III, Trisha Gee, Attila Szegedi, Sven Peters, Kohsuke Kawaguchi, Dan Allen, Adam Bien, Markus Eisele, Gene Kim, Arun Gupta, Jevgeni Kabanov, Anton Arhipov, Simon Maple and Geert Bevin–all have one thing in common…

They write. A lot. And what they write turns into books that developers download or buy, presentations developers peruse and talks that developers listen to. Why do you think they do this in their extra hours?

If you have ever been to an IT event, you’ll remember that speakers at conferences are industry rockstars, well-known and thought of first when it comes time for that new idea or project to get started. It comes down to a question of visibility. Published authors are more visible than “corner coders” (i.e. headphones on, heads down, and, if in large teams, sometimes seen as just one of the ranks) :-/

Final thoughts

Managers and team leads should be informed of all the merits that come when your development team spends a few hours each week reflecting and reviewing their work. Developers who take some time out of their work week (if feasible) or allocate some extra hours (if possible) for writing each week or month are doing themselves a great service. Starting slow seems to work best: Write 1 paragraph (or just even a Tweet!) about what challenged or interested you this week. And again next week. Easy.

You can quote me here: I cannot think of a more simple and yet so highly-beneficial way for developers to improve their minds and thought processes, so that their code and daily work improves, resulting in a better network and career prospects as nice little cherry on top.

Confession: I have a selfish goal in mind with this article: to invite the best engineer-writers out there to become RebelLabs Authors. It’s no secret–and I’ll be blogging soon about how specifically RebelLabs can help these 3 points become realities for you.

So there you have it. I invite you to please share this article, leave comments below or tweet me @theotown. May the [writing] forces be with you.