: Re: Can technical writing suck less I currently have the prospect of writing a considerable amount of technical documentation (describing interactions with an extremely complex online service). I consider
I think what you are missing is that all writing tells a story. Just because there is no love story or car chase, that does not mean your technical writing is not telling a story. You are just telling the story of hooking up a Chromecast. That is actually an exciting story for people who just got a Chromecast. They are your characters! Don’t diminish their excitement with crappy writing. Get excited along with them — we’re Chromecasting! — just as you would get excited along with a fictional character who is falling in love or having any adventure.
Get your head right, get into the story, and then write a personable, concise, helpful, plain language, understandable-by-all guide to Chromecasting that is a joy to read and use and that improves people’s lives by making their new Chromecast setup into a fun event with maybe a minor pitfall here and there that was easily solved, rather than a horrible chore that robbed them of hours of their precious life and then left them disappointed.
Instead of a fictional character waiting for you to tell them what to do, you have a community of real characters waiting for you to tell them what to do. You can make a million lives better with great writing. It is a serious responsibility and a great opportunity to grow as a writer and as a person.
More posts by @Eichhorn147
: I think whether or not you can get the book “published†is irrelevant. I recommend you don’t even concern yourself with that. In the first place, you can publish it yourself, on your
: How to avoid the 'magic explanation' info dump in Fantasy novels In the second book of his Inheritence Cycle, Christopher Paolini makes the grievous error of landing his main character in the
Terms of Use Privacy policy Contact About Cancellation policy © selfpublishingguru.com2024 All Rights reserved.