DEV Community

Discussion on: Why Every Developer Should Write

Collapse
 
darkwiiplayer profile image
𒎏Wii 🏳️‍⚧️

Write consistently (ie, set a publishing schedule)

I think this is very counterproductive. Nobody will constantly have something of value to say, and forcing it will sooner or later lead to generating content for the sake of content.

I think there's a lot of value in knowing when to speak and when to stay quiet, and this applies just as much to writing. Knowing what topics are worth writing on and which aren't is essential to building a reputation of quality over quantity.

Collapse
 
tmchuynh profile image
Tina Huynh

I definitely agree on this point. I wouldn't encourage someone to write to simply write - I think that got misinterpreted. My apologizes. But building better writing skills, like any other skill, requires dedication and practice. This doesn't mean one has to do it every day or every week, but if they would like every once in a while. Practicing always helps.

Collapse
 
darkwiiplayer profile image
𒎏Wii 🏳️‍⚧️

Also:

Use correct titles (not click-baits) and deliver on your topics

Absolutely not. Use correct titles, but do make them click-baity. The most amazing post can fail to gain any attention if the title doesn't manage to show off how exciting the topic is. What matters is quality. Avoiding inflationary use of words and expressions like "AMAZING" or "WILL CHANGE YOUR LIFE" (in all caps, of course) in favour of more subtle techniques (like relating the topic of the article to the reader à la "How XXX can help you with YYY") will make a title "seem" a lot less click-baity, while still drawing in much more attention than something dry like "An analysis of XXX".

Delivering on the topics is, of course, a must. But not lying to the reader should be obvious without anybody pointing it out :D

Collapse
 
thumbone profile image
Bernd Wechner • Edited

Precisely the problem with today's blogging culture. Endless trash being written and rewritten and copied and paraphrased.

Write when you feel you have value to add to the community.

Collapse
 
ludamillion profile image
Luke Inglis

I agree strongly with one aspect of what you are saying but offer a counter to it as well. Writing consistently is very important to being a good writer but knowing when to publish and only doing so when you have content worth publishing is the key.

It is important to keep yourself writing on a schedule but feeling compelled to publish everything you write or feeling like you always need to generate 'content' doesn't help anyone. As you say it causes the writer to focus on quantity over quality thus losing much of the personal value of writing and, for lack of a better word, pollutes you output with lower quality content thus losing the 'social' or 'branding' value of writing.

Collapse
 
darkwiiplayer profile image
𒎏Wii 🏳️‍⚧️

For someone intending to make writing into their profession, this is probably true, but for your average developer, it's probably more than enough to simply write whenever there is something worthwhile to write about.

Just an article or two is already a good bit of effort, and if it's about a topic that can't be googled in 5 minutes, there will probably be a good bit of writing, deleting and re-writing involved.

Combine that with other writing tasks that just come with the field, like writing documentation, and you'll already be doing a solid amount of writing practice, certainly more than many other professions.