Stephen King: “Everything You Need to Know About Writing Successfully”
msu.edu
msu.edu
The writing part should be interesting to anyone who: likes reading fiction and thinking about how it is created; likes writing and has spent time about how to do it well; has spent time thinking about how to a particular thing well.
Incidentally, Stephen King ended up actually putting that scene into one of his novels, the seventh book of the Dark Tower. This was fitting, I thought, since the idea of the Dark Tower is that it contains all worlds, real and fictional, including our own.
Funny thing is, the two elements I remember the most from what I learned inside are at what could be considered both extreme of the "importance spectrum": double the s (the kids's toys) and don't write adjectives to give feelings and emotions when your task is to create them (if something is awesome, don't write "it's awesome", make it read/feel/look awesome).
And counterproductive? King's approach to plotting is described as essentially thinking his characters into difficult situations and then figuring out the details of how they'll extricate themselves as he goes along. This works very well for Stephen King, but certainly isn't the only way successful authors approach plotting, and some of the meticulous planners are extremely good and successful writers too. It's people that don't have an innate flair for structuring novel length texts as they go along that are most likely to pick up books with titles like "on writing" though...
As an autobiography and homage to his passion, it's brief and very readable though.
Also interesting is that I think King's latest movie, A Good Marriage (2014), may have been loosely based on an idea he submits as a exercise to the reader in On Writing: iirc, King describes a situation which involves a woman estranged from her abusive husband being home alone while the child is at school and the husband unexpected comes into the house.
King asks the reader to write a short story based on this situation and send him and to send him an email with the story and the readers thoughts and how they came to write it.
I've not seen the movie or read Full Dark, No Stars (2010) that contained the novella it is based on, but that situation seemed similar.
For the HN audience, #4 is the most relevant one. Too many things I read here have high school-level writing. The authors cared more about getting their half-baked opinion out on their Medium blog over proofreading (excluding ESLs). One of the best lessons from college is when one of my history professors metaphorically tore me a new asshole for not knowing how to write on one essay, and out of pity, gave me a grace period to fix it. He highlighted enough of my superfluous fluff that I finally got writing and how one must write as little as possible. I had other writing-intensive classes after that one and never had such an event happen again.
Right, because Joyce, Pynchon, and Nabokov would have benefited from being told to write "as little as possible".
If you're writing non-fiction, maybe. If you're writing literature, to hell with rules. How impoverished our culture would be if all writing held itself to the same standard.
They might have. Especially Pynchon, but Joyce too.
I was afflicted with having to read "Portrait of the Artist as a Young Man" in high school. In it, Joyce puts forth his theory of art - that to be pure art, it should cause no response whatsoever in the viewer. Joyce is a great writer, and was able to achieve the effect he wanted - to write a book that produces no response whatsoever in the reader (other than the feeling of revulsion at being forced to waste my time reading it). But because his theory of art is rubbish, he wastes his talent producing "art" that is a complete waste, both of his talent and of the reader's time.
At any rate, even if that really was the goal he set for himself, he failed. Ulysses elicited a wide range of responses from me.
I mean, there was a scene or two in Portrait that I responded to, too. But mainly, it was a protagonist I didn't care about, doing things I didn't care about, with other people I didn't care about, in places I didn't care about. So "no response whatsoever" is a pretty fair summary of my reaction.
The tragedy of Portrait is that so many people read it as if it were simple autobiography. It isn't. Stephen is based on the young Joyce, yes, and in the original draft and notes (mostly destroyed, published as Stephen Hero) there's a saccharine sincerity that fits your sense of the book a little better.
But that's not the finished Portrait. In Portrait Joyce makes fun of himself. He's critical of his youthful exuberance. It's a hilarious book for anyone who's ever taken themselves too seriously, which, I think, is all of us.
"Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away" - Exupery
"A witty saying proves nothing." - Voltaire
I have had to put more than a few books down because the author was putting a lot of words down, but not really saying anything.
I think the content/word-count ratio is important.
Well, that's not true. Jules Verne.... I could never finish 20,000 Leagues under the Sea despite being immensely interested in the story as a youngster.
I personally believe that programmers can learn from poets, for example. Write constantly. Read the work of others, both critically and for enjoyment. Writing is the sexy part, but revising is at least as important a task.
I find it also sometimes helps to perform the revisions while in a somewhat altered state of mind (be it mood, setting, music, minor inebriation, or otherwise). It helps you look at the first draft with fresh eyes and see better ways of structuring things and removing excess. Make a version with your prospective changes, then compare the before and after copies a day or two later (this time sober if you weren't before...).
I think it belongs - What he is suggesting carries over to technical endeavours as well.
1. Learning to cut mercilessly improved clarity of my emails and documentation.
2. Learning to put my head down and carry on till a project is first draft complete, warts and all improved my ability to actually _complete_ things.
3. Peer review as a bullshit detector is good.
I'll take Poe or Lovecraft over King any day for entertainment, but I might just crack 'on writing' after reading this article. The man sounds pretty dialed in.
What I found really neat about King's advice is its practicality. This, I think, makes his points applicable to young writers as well as young entrepreneurs, esp. (1) and (7) can be combined to pg's motto of "Make smt that people want."
> 8. Ask yourself frequently, "Am I having fun?"
> The answer needn't always be yes. But if it's always no, it's time for a new project or a new career.
Reminds me of this quote from Steve Jobs's commencement address[0]:> When I was 17, I read a quote that went something like: "If you live each day as if it was your last, someday you'll most certainly be right." It made an impression on me, and since then, for the past 33 years, I have looked in the mirror every morning and asked myself: "If today were the last day of my life, would I want to do what I am about to do today?" And whenever the answer has been "No" for too many days in a row, I know I need to change something.
[0] https://news.stanford.edu/news/2005/june15/jobs-061505.html
A good companion piece. Really, if you want to know how to write, and barely have time to make breakfast, The Elements of Style is the book for you.