DEV Community

Cover image for Three Arguments for Why You Should Write More

Three Arguments for Why You Should Write More

Marek Zaluski on January 28, 2019

Let me try to convince you to write more. I don't mean write more code. I mean write for humans. There's a huge benefit to getting good at writin...
Collapse
 
phoinixi profile image
Francesco Esposito

Thank you for sharing this! Very motivational 🙂

Don't have anywhere to post it? Post it on dev.to.

This exactly what I am doing, starting my journey in sharing my thought, writing simple posts.

My writing skills are pretty basic and my vocabulary still poor, but from somewhere we need to start, right? 🙃

Collapse
 
lechenco profile image
Gabriel Lechenco

Yeah! I'm trying to do the same. And I don't have English with my native language, so writing here it is a way that I found to push me over and improve my skills.

Collapse
 
tcelestino profile image
Tiago Celestino

It's same here.

Collapse
 
sandordargo profile image
Sandor Dargo

I agree with your article, but I'm troll enough to make a remark on this phrase: "I don't mean write more code. I mean write for humans."

According to some of the finest computer scientists, code is written primarily for humans:

“Programs are meant to be read by humans and only incidentally for computers to execute.” ― Donald Knuth

"Programs must be written for people to read, and only incidentally for machines to execute." - Abelson & Sussman, "Structure and Interpretation of Computer Programs"

Are their points still valid? That might be the topic of another article.

Collapse
 
qm3ster profile image
Mihail Malo

For sure, no?
Otherwise no one would use say... TypeScript? Which contributes nothing to the runtime.
Nor would anyone ever leave comments.
One can even make the argument they would not use a high level language at all, but that's the iffy one.

Collapse
 
berkmann18 profile image
Maximilian Berkmann

They are still valid, why?
Because, unless you only do code golf and throw away all the code you write, you'll be writing something that someone (including the future you) will be reading and trying to maintain, fix and what not so it's important that the code is readable.

One might say, your code should be self-documenting so no documentation is needed, I'll argue that it would depend on several things but we're not discussing about documenting code vs not doing it.

Collapse
 
triptych profile image
Andrew Wooldridge

This is good advice. I would only add to try to write for your own domain first and cross-post to places like medium and dev.to to get maximum benefit. Also, after say 6 months of writing -- roll that up into a book and self publish!

Collapse
 
codemouse92 profile image
Jason C. McDonald • Edited

As an author who founded his own publishing company (one step beyond standard 'self-publishing'), with many years exposure to the writing industry, I'd like to add a few points to the "roll that up into a book" comment: It isn't something you want to do on a whim! Successful publishing requires extensive planning and a potentially expensive initial investment.

  • Plan your content. Any effective book still has to have a cohesive structure, even those which are collections of essays (For example, The Cathedral and the Bazaar or The Size of Thoughts: Essays and Other Lumber.) Unless you're E.B. White, no one will want to read a random collection of your articles/essays if it doesn't have a cohesive theme.

  • Get it edited professionally! Too many authors skip this step, or assume that if their Aunt Ruth didn't find any missing commas or spelling errors, it's good. Real world editing goes far beyond proofreading, and is essential any book's success. Find at least one reputable professional editor. If possible, you should also get several of your industry peers to read the book as well and offer their constructive criticism.

  • In concert with the editing step, prepare to revise heavily. Even the best author has to edit, tweak, and revise their book repeatedly before it has any chance of success. It really does take a village to publish a book.

  • Get it designed properly. Unless you're like me, and have an inexplicable knack for typography and typesetting, you'll want to find a professional book designer. Some printers offer these services for a fee. "Good enough" is not good enough. (By the way, print and ebook have to be designed separately.) While you're at it, be sure to get a good cover designed!

  • Beware most self-publishing schemes. Read consumer reports from independent sources, and select your printer carefully. All legitimate, worthwhile printers and publishers will pay you pre-arranged royalties on every single sale; printer setup fees should by well under $500 (not counting ISBNs, design work, or marketing). I use IngramSpark (LightningSource), which offers the industry's best distribution. BookBaby and CreateSpace are other options, although they both have limits and drawbacks. Alternatively, consider submitting to a relevant, independent publisher like No Starch Press.

  • By the way, to sell the book, you will need one ISBN per format, e.g. one for paperback, one for ebook (any type). Bowker is the only place to buy these legitimately - ISBNs from anywhere else are either recycled (and thus worthless) or fake. Some reputable printers may offer to resell an ISBN from Bowker to you, however; just make sure they did get it from Bowker, not elsewhere! (Ingram and BookBaby both offer this.)

  • If you're doing this all yourself and getting it printed, consider registering the book with the Library of Congress (through their PCN program). By doing this, your book can be carried by libraries; otherwise, they won't touch it.

  • Be sure to consider the legal, business, and tax components here. Does your state require you to register as a business if you're collecting royalties? (Some do.) Do you need a retail license? Would an LLC be a wise investment, to keep your personal money out of any possible legal tangles? Self-publishing should not be approached on a whim; you need to understand all the implications of your publishing endeavors.

These steps are all applicable, even if you "just want to publish an ebook on Amazon". Otherwise, your work is fated to be nothing more than an occasionally shared free download, and a tremendous waste of your time and money.

Collapse
 
marek profile image
Marek Zaluski

Great to have your input on the book publishing world, that's really useful to know.

Collapse
 
rmhogervorst profile image
Roel Hogervorst

If you want to write better, I highly recommend writing without bullshit by Josh Bernoff. It's extremely readable, and it gives great pointers that I never got anywhere else.

Collapse
 
kristiyanpeshtenski profile image
Kristiyan Peshtenski

Thanks man!
Really nice article.
Writing well is an extremely useful skill, witch unfortunately I do not have yet.
I read many similar posts, and every time It motivates me to start, but never DO anything.
This time will be different.
I will start with small steps. First one is to write that comment.
Hope that will be the beginning.

Collapse
 
egimba profile image
Eric Gitonga

I had just started out the initial words of a post when I came here to check on something, and this is the first post I came across. The universe telling me something? Anyway, I have decided that I shall get my writing chops on by documenting my journey to learning R. More as notes to self. Thanks for this pep talk!

Collapse
 
shaikhul profile image
Shaikhul Islam

Communication is a skill that's overlooked a lot by developers

true story.

Thanks for sharing!

Collapse
 
kicksent profile image
Nick Trierweiler

You have a typo in your post: "all it takes it practice" should be "all it takes is practice".

Very nice post. I will certainly be using this to document my work for my team mates to use. I liked the section about over-communication. Over communication saves time in the long run and only takes an extra few seconds which can add up quickly. For a bonus, you should plan how to explain what to communicate briefly and then communicate it as thoroughly as you can.

Collapse
 
ant profile image
Ant

this article really encourages me,I can't agree more

Collapse
 
teleyinex profile image
Daniel Lombraña González

Good article. Actually, as a bonus, if you don't mind, write in paper with a ballpen. Why? There's some literature that says that writing with a pen will get your memory better. Thus, write it and if you can with a ballpen (I've just started to do some #bujo, hopefully to improve on this as well).

Collapse
 
craigbutcher profile image
Craig Butcher • Edited

Your post nailed it on the head!

I have been persuaded by a few people when am I going start writing blog posts again. I have been out of the loop for a few years and found a sense of imposter syndrome to anxiety who is going to be reading my 'crap'.

Collapse
 
steelwolf180 profile image
Max Ong Zong Bao • Edited

Awesome article actually for me, writing has always been a pain in the butt for me since my command of English is awful since I was young.

But what I do desire is the process of creating ripple effects to a bunch of people through my writing.

Besides that, it serves as a place for me to reinforce my understanding of technology.

A side benefit is that it serves to document my process as I grow as a developer in my chosen niche and specialisation.

Collapse
 
lepinekong profile image
lepinekong • Edited

Fully agree, virtue comes with habits. Nevertheless I have asked developers in my team to do so, they're very reluctant, and I understand why: it's very time consuming, that's why I'm working on a system to lower the effort with readable.red it's not finished and documented yet, just a preview as I'm experimenting with it myself first see example redlang.red/collect :) I'll also use it to write tutorials for dev.to in the future (see past ones dev.to/lepinekong/red-for-hopeless...).

Collapse
 
phantas0s profile image
Matthieu Cneude • Edited

Thanks for this blog post! I love writing myself, I can only agree with most of this article.

Here's a good strategy for any team of developers: over-communicate.

Over communication is not necessary good either to me: miscommunication and confusion can come because you explained too much. Whatever the amount of communication, it's more important to be precise and clear.

If you over communicate and contradict yourself at the same time or provide clear and then confused explanation, expect some wrong results.

Communication is a skill that's overlooked a lot by developers.

This is really true. I think communication is utterly important for developers.

Collapse
 
rachelsoderberg profile image
Rachel Soderberg

I started doing a weekly blog-ish post writing about something I learned in the week related to software or tech at the beginning of the year... but I fell off and missed a couple of weeks. Thanks for the kick in the rear to get back on that. :)

Collapse
 
berkmann18 profile image
Maximilian Berkmann

This is definitely inspiring me to write.
The problem (if we can call it a problem) is that I'm on DEV.to, Hashnode, Medium and currently in the process of trying out some frameworks and tools that I will use to create my new website and my blog.

Collapse
 
karataev profile image
Eugene Karataev

Great post, thanks.
I've indeed noticed that day-to-day writing (emails, posts, comments, documentation, commit messages) really improves the speed of transformation thoughts in a brain to the words in a text editor.

Collapse
 
panditapan profile image
Pandita

I pretty much dedicate myself to fixing bugs and I've never written a bug report...

I think I'll start.

Thanks :3

Collapse
 
simoroshka profile image
Anna Simoroshka

With own blog, you need to think about attracting readers which is an entirely different story.

Collapse
 
pavelloz profile image
Paweł Kowalski

I don't mean write more code. I mean write for humans.

Some might argue, that we write code for humans - on so many levels. :)

Collapse
 
tomavelev profile image
Toma

I have similar thinking about writing (and not only code or blog) dev.to/tomavelev/social-networks--...

Collapse
 
mdhesari profile image
Mohammad Fazel

Thank you Marek!
Any tips or resources for writing better?

Collapse
 
jimmy1702 profile image
jimmy1702

Here a list of best writing services. Most of that company's have blog with tips or resources for writing better.

Collapse
 
nathanenglert profile image
Nathan Englert

Love this article, pinning it for when I need another dose of motivation.

Collapse
 
chuksjoe profile image
Chukwunonso Orjiakor

WOW!!! this really got me and I think I belong to the 3rd category.
Thanks so much for challenging me.... Look out for my first post soon.

Collapse
 
lauragift21 profile image
Gift Egwuenu

This was a very insightful read! Reason 2 and 3 was why I started writing and I can say over the last couple of years my writing has definitely improved!

Collapse
 
chuksjoe profile image
Chukwunonso Orjiakor

WOW!!!.. this really got me, and I think I belong to the 3rd category.
Thanks for challenging me, look out for my first post soon.

Collapse
 
tcelestino profile image
Tiago Celestino • Edited

Years ago I've written a lot but the last years I stopped to write and I started read a lot.

Collapse
 
codyevans3 profile image
Cody Evans

Apparently you moved to a new level;)

Professionalism comes with practice. The more you write, the better your skills become. I made a list of best writing services in 2019, these guys write a lot...