Skip to main content

Book Review: Writing Tools: 50 Essential Strategies for Every Writer by Roy Peter Clark

I wanted to read something outside of my comfort zone. As I try to learn English and I am writing blog posts in English it seemed like a good idea to read something about writing. My choice of a book was more accidental than deliberate, but I am pretty happy with what I have learned.

Of course, it did not make me a writer in a couple of hours. I have gained some insight into writing, practical use of grammar and structure of stories that was interesting just in itself, but there were also some more general ideas included.

How to think about writing, how to deal with critics and knowing your colleagues and they craft (like photojournalism and design) can be applied to any craft you do. Writing big books, should be divided into chapters, parts, that you can think about - something that fits in your head. It is much too easy to be overwhelmed by a 300 pages you have to write. Divide those into smaller parts.
When you write the first version, you should lower your standards. Treat it like a draft, use cheap paper, do it one page at a time. Whatever helps you. Procrastination often rises out of perfectionism. You can't meet those high expectations of yourself at the very first steps. Fool yourself into making any work with low standards so later you can build on top of it.
When someone criticizes work you done, what do you do? If you are like me, you get defensive or you try to diminish the importance of the critic. Author suggest to instead to explain why you did things in that way in the first place. Explanation of your reasons can lead to a conversation from which you can learn something new.
Have you ever argued about a film you liked that someone else just not seem to understand? If you are a JavaScript programmer you might have argued about automatic semicolon insertion. Turns out, those cases share one common trait - you were arguing about tastes. Unfortunately, they cannot be changed by arguing about them. You cannot please all tastes at once, choose the one you prefer and avoid arguing about it, do not waste time.
Learn other crafts. Buy a book about work your colleagues do. Read about photography and design. Learn the vocabulary and ask your peers how you can help them make their best work possible.
Create feedback circle. Ask people around to help you, give your feedback, encourage you. This way you can get feedback and will be happier in the process.

Of course, the most important tool to use is reading aloud what you wrote. I am not doing that. I am not always reading the posts I wrote before publishing them. This has to change. I also have a plan to ask for feedback before I publish a post. Those two will make my posts longer to write, but increase their quality.

Rating: 6/10

Extra: Have you seen Grammarly? It is a really nice service with Chrome extension that finds much more errors than standard browser checker. I use the free plan and it already helped me fix numerous errors. Highly recommended.


Popular posts from this blog

Course Review: The Bitfountain iOS 8 with Swift Immersive

This is second big iOS learning project. For first one read iOS Programming book review. As I only have two of them done I have to compare them somehow.

I am mindful that it took me a really long time to finish it (since last autumn). For a couple of months this year I didn't even have the internet to learn it, so it could not be helped. But last half of the June I've spent watching the videos every day and managed to finish it before any new internet problems.

So how was it?
In my opinion, it's great if you're starting out. There are a lot of basics, and seeing how to do things in XCode just makes your learning much easier than looking at the photos in the book. On the other hand, learning is more shallow and it is much easier to just follow the videos and learn only the basics without bigger picture about iOS SDK. I somehow missed more challenging exercises (even though I don't like to do them ;)

Course it pretty long but many videos are quite short (1-2…

How to Learn when Life is Short

I haven't really think this through but I have read really interesting articles recently and I just wanted to write for myself later.

Life is Short by Paul Graham

It's just that, learn from people older that you what is most important, and that life actually is short...

Instead of Goals or Resolutions, Try Creating Rules by Leo Babuta

In the time of New Year Resolutions, it's good to read something that is proposing different way of achieving things. Still I see much more value in habits than setting goals. But...

The Easy Way To Learn Hard Stuff by Per Harald Borgen
It's something that I read from time to time and I know it works sometimes for me. The things I learn then are really learned and something Jakub Wasilewski  has told me many times to do. Still it's uncomfortable and for some reason, I have failed to use this method more than once or twice. Writing it here so maybe I can think about it more and figure out how to do that more often.

Towards an understandin…

Hero's Journey in Presentations

Artur Skowroński recommended me: Want a Better Pitch? Watch This. by Andy Raskin and I think it is so great and applicable to all kinds of talks that I want to help it get more popular.
So the plan of presentation is going to follow these steps: Enemy - ProblemWhy now? - call to actionShow how the world will look like without the problemProblemsEvidence that you fixed the problem The image at the top is because it reminds me of Hero's Jurney. It has fewer steps but there is a lot of similarities. Especially #3 made me realize that grand vision of the future is something that I should have used in my talks.  The result at the start of the presentation makes a lot of sense actually. Everyone already knows that I speak about something because I probably fixed it and if you tell about it at the end then it might be hard for some people to see the bigger picture in the solution you're going to present.