{"id":25823,"date":"2022-03-29T08:59:51","date_gmt":"2022-03-29T06:59:51","guid":{"rendered":"https:\/\/www.wbscodingschool.com\/?p=25823"},"modified":"2022-03-29T08:59:51","modified_gmt":"2022-03-29T06:59:51","slug":"blog-how-to-write-a-tech-blog-that-reads-well-1","status":"publish","type":"post","link":"https:\/\/www.wbscodingschool.com\/blog\/blog-how-to-write-a-tech-blog-that-reads-well-1\/","title":{"rendered":"How To Write A Tech Blog That Reads Well \u2013 #1. Fundamentals"},"content":{"rendered":"\n

I have a bit of a strange relationship with tech blogs. On one hand, I want to see more of them and I\u2019m constantly telling every developer I meet that they should give a shot at writing one.<\/p>\n\n\n\n

On the other hand, and much as I hate to say this, most published writing that is about tech is of pretty dismal quality. I don\u2019t mean that the contents<\/em> are necessarily bad, rather the writing in and of itself<\/strong> \u2013 its style, its elegance, its focus, its precision.<\/p>\n\n\n\n

The reasons for this are various and I\u2019m not going to explore them now. I\u2019m not here to point fingers at anyone.<\/p>\n\n\n\n

Instead, what I would like to do with this series is to offer a guide on how to write a blog \u2013 or any other kind of short personal article \u2013 that is compelling, elegant and a pleasure to read. Because there is very much to be said, I will be publishing one article a week for the next six weeks<\/strong>, in which I will cover everything from structure and style to opening and closing your blog.<\/p>\n\n\n\n

This is not<\/em> a guide on how to market, sell, or distribute your content, which is a wholly separate topic<\/strong>. If that\u2019s what you\u2019re looking for, there are plenty of resources already out there \u2013 here is Backlinko\u2019s definitive guide to SEO<\/a>, for example.<\/p>\n\n\n\n

I offer the content of these articles as friendly advice, and not as a rulebook. I am not a university professor in English or any other discipline, only a professional content creator who has written articles in a wide variety of fields and consistently attracted readers in the thousands or tens of thousands.<\/p>\n\n\n\n

If you don\u2019t like my advice and choose to ignore it, more power to you \u2013 I certainly do not claim to be the ultimate authority on writing, and I wish you the best of luck with your approach!<\/p>\n\n\n\n

If you do choose to welcome my advice, then you will find it structured as follows:<\/p>\n\n\n\n

Article #1 \u2013 Fundamentals & Essential Practices<\/strong><\/em><\/p>\n\n\n\n

Article #2 \u2013 Structuring Your Blog & Presentation<\/a><\/strong><\/em><\/p>\n\n\n\n

Article #3 \u2013 Style<\/a><\/strong><\/em><\/p>\n\n\n\n

Article #4 \u2013 Common Pitfalls<\/a><\/strong><\/em><\/p>\n\n\n\n

Article #5 \u2013 Opening Your Blog<\/a><\/strong><\/em><\/p>\n\n\n\n

Article #6 \u2013 <\/i>Closing Your Blog And Explaining Difficult Concepts<\/a><\/strong><\/span><\/p>\n\n\n\n

Right now, of course, you are reading Article #1. So let\u2019s get started with\u2026<\/p>\n\n\n\n

THE FUNDAMENTALS \u2013 GRAMMAR, SPELLING, SENTENCE STRUCTURE.<\/strong><\/h2>\n\n\n\n
\"Business
Adobe Stock \/ jakkapan<\/figcaption><\/figure>\n\n\n\n

Nowadays, many and possibly even most of those who write tech blogs in English are not themselves mothertongue English speakers. Of those who are, many may not have had the opportunity to study how to properly write in English since high school.<\/p>\n\n\n\n

There is nothing wrong with falling in either of these categories, nor should that make you feel intimidated about trying to do some writing. However, it does mean you have to put some extra effort to ensure before anything else that you can write in good English<\/em>. Not \u2018passable\u2019, not \u2018serviceable\u2019, not \u2018ok\u2019 \u2013 good<\/em> English.<\/strong><\/p>\n\n\n\n

This means that errors in spelling, grammar, syntax and punctuation are not acceptable. If you are consistently making these mistakes, they must<\/em> be ironed out.<\/p>\n\n\n\n

Fortunately, modern tools to handle this issue are abundant, starting from Microsoft Word\u2019s autocorrect feature to software like Grammarly<\/a> and Hemingway Editor<\/a>, which will automatically check and optimize your grammar, spelling and sentence construction.<\/p>\n\n\n\n

Full disclosure \u2013 I am actually not a huge fan of that type of software myself. In fact, for writers who already feel confident about their language skills, I would advise against<\/em> using crutches like Grammarly, as they have the unwelcome side effect of dulling your personal voice.<\/p>\n\n\n\n

For anyone who isn\u2019t already advanced, however, there is no question that these tools are a must. They will let you publish articles that are stylistically acceptable even if your English levels still have a way to go.<\/p>\n\n\n\n

If you really are committed to improving, you can also give a read to some basic writing guides, like the excellent \u2018Eats, Shoots and Leaves\u2019 by Lynne Truss<\/a>. They can be incredibly helpful, and not just for the beginner \u2013 even the best of us don\u2019t have perfect mastery of the language!<\/p>\n\n\n\n

ESSENTIAL PRACTICES<\/strong><\/h2>\n\n\n\n

1. REVISION \u2013 HOW MUCH?<\/strong><\/em><\/h3>\n\n\n\n

If you write, you should be familiar with the concept of drafting<\/em>. Your first version of an article will always be a draft<\/em>, and you should see the completion of the draft as a stage<\/em> of the writing process, not as the end of it.<\/p>\n\n\n\n

\"Young
Adobe Stock \/ Elnur<\/figcaption><\/figure>\n\n\n\n

You should never \u2013 and I mean never<\/em> \u2013 publish an article you wrote without having re-read it at least a few times.<\/strong> Re-reading allows you to pick up on problems with the text that your mind did not register during the more intense creative phase, and to correct them.<\/p>\n\n\n\n

Exactly how many times should you re-read your text? This is often subjective, but here is one revision routine I feel I can recommend:<\/p>\n\n\n\n

  • Day 1:<\/strong> This is the day in which you have finished your first draft. (Not necessarily the same day in which you started it, of course). We will start our count here.<\/li>
  • Day 2:<\/strong> First, revise the draft while it is still fresh in your mind, i.e. no more than a day after it was finished.<\/li>
  • Day 3-5:<\/strong> One more bout of revision to clean up anything you missed the first time. This should be a quick and easy one.<\/li>
  • Day 10-12:<\/strong> After a one-week break, revise the text again. If you are happy with it, time to publish. Otherwise, back to step b.), and repeat the process as many times as necessary<\/strong> until you\u2019re happy with what you have written.<\/li><\/ul>\n\n\n\n

    You should absolutely be open to the idea that your article may change heavily from the first to the second and possibly from the second to the third draft. And there should always be a break of at least one week before the final revision<\/strong>, as your brain will actually fail to register imperfections in your own writing if you don\u2019t take some distance from them. I have sat on some of my more complex article for months<\/em> at a time, pushing them as far as possible to the back of my mind so that I could return to them with fresh eyes. The process always pays off.<\/p>\n\n\n\n

    Unless your article is time-sensitive for whatever reason, I would always recommend waiting rather than publishing something you are not 100% confident about. You\u2019ll find whatever it is that is nagging at you, I promise \u2013 you just need to give yourself time.<\/p>\n\n\n\n

    2. READING OUTSIDE OF TECH<\/em><\/h3>\n\n\n\n

    Reading the work of others is an indispensable practice to get better at any kind of writing. It will expand your vocabulary, refine your sense of phrase, and give you a ton of new ideas.<\/p>\n\n\n\n

    When it comes to tech, however, there is a problem. As I mentioned at the outset, the writing standards are unfortunately not very high. There are some excellent technical articles out there, but it\u2019s quite rare for them to be exemplary in terms of writing style.<\/p>\n\n\n\n

    I would therefore strongly recommend regularly reading material about non-tech topics.<\/strong> For the purposes of getting better at writing blogs and articles, reading journalism is probably preferable to reading fiction. The latter is much more creative and sophisticated in its use of language, but often too much so, leading blog writers to write wordy and convoluted material.<\/p>\n\n\n\n

    By contrast a subscription to a reputable news publication like The Times<\/em>, The Economist<\/em> or The Guardian<\/em> will give you a more realistic sense of what sort of language is adequate for an article, as well as how to structure one. Avoid tabloid journalism please \u2013 the style there is as trashy as the content.<\/p>\n\n\n\n

    Naturally, you should also be reading tech-related articles to get a sense of what sort of content is popular, to learn from others, and to find new ideas. Just be warned that most of this material will not do much to improve your writing style.<\/p>\n\n\n\n

    ***<\/p>\n\n\n\n

    All right! This covers Fundamentals & Essential Practices. If this seemed a bit basic to you, well \u2013 that\u2019s what the fundamentals are supposed to be!<\/p>\n\n\n\n

    Join us next week as we cover the topic of structure<\/em>.<\/p>\n","protected":false},"excerpt":{"rendered":"

    An in-depth series on a topic that needs more attention<\/p>\n","protected":false},"author":17,"featured_media":46357,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","footnotes":""},"categories":[45,42],"tags":[],"class_list":["post-25823","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-careers","category-coding"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/posts\/25823","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/comments?post=25823"}],"version-history":[{"count":1,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/posts\/25823\/revisions"}],"predecessor-version":[{"id":62577,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/posts\/25823\/revisions\/62577"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/media\/46357"}],"wp:attachment":[{"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/media?parent=25823"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/categories?post=25823"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wbscodingschool.com\/de\/wp-json\/wp\/v2\/tags?post=25823"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}