How to edit your own lousy writing (2017)
stingingfly.org
stingingfly.org
This is what almost everyone on the internet gets wrong these days, especially writers on medium and other blogging platforms, but also writers on the BBC and the Guardian. Their articles are too long and padded.
I guess I can't fully blame them. Google prioritizes lengthy texts as a signal of being authoritative and comprehensive. Most texts these days are twice as long as they need to be.
Apparently also said by Locke, Franklin, and a bevy of other famous figures too. Good advice, even if the source is unclear.
Quality can also vary wildly of course. Tight writing also applies to long-form. You do not want to end up meandering.
Sometimes they fall far short of that goal
I think I agree with you
If I am reading Gauss, my mind wants to process facts immediately.
If I am reading the New Yorker, my mind would like to wander a bit.
It all depends on what you are reading.
A new yorker style article explaining for loops in a programming language. Yeah nobody wants that.
Small subthread derailment - nonfiction books which are worth the full length. I'll start:
The Making of the Atomic Bomb; Gödel, Escher, Bach; The Ancestor's Tale; Bad Pharma
I once got into an argument with the teacher for a psychology elective. I asked her to indicate which oft the expected aspects I did not address, but she said she didn't even read it because "it was too short so it couldn't possibly cover everything". I padded it with a bunch of meaningless fluff, resubmitted it and it was accepted.
All through middleschool, highschool, and college every writing assignment has had a minimum word or page count.
Sometimes we had maximum requirements, but oftentimes just a minimum.
I was nearly a straight-A student on writing assignments in college. I'd often write well below the minimum requirements by filling out my outline, then I'd add fluff around it to reach the minimum words without actually adding any meaningful content, still scored fine.
Truly a profound waste of time.
Similar story here. In college I got extremely good at adding fluff to reach minimum word counts, I performed well on almost all writing assignments doing this. I would write an outline, fill it out with useful information, and then turn a couple sentences of actual content into multiple paragraphs each.
What a way to fuck up my day :)
I don’t think they realised that by lowering (or removing) a single integer on the guidelines, they would improve the lives of students, the faculty, and everyone who will ever read those papers.
because the algorithm rewards this. Which algorithm you ask?
all of them.
This is the biggest difference between poor writing and a masterpiece.
For example I just watched episode 2 of the new Star Wars series Ahsoka — where two characters literally tell each other the backstory… for ten minutes.
It’s like listening to two school students reading out the plot summary of a novel.
Weird how the same organization wrote the brilliant Andor!
Ahsoka is part of the larger canon of things like the clone war cartoons and a handful of random episodes in newer Disney shows. Most fans have no idea about her, the post-ROTJ world its set in, Thrawn, etc. Its a lot to ask to slow burn that.
Also you can slow burn that if you truly wanted, but it comes at a cost. The writers weren't willing to make that sacrifice of other story elements, characters, sub-plots, etc to do this.
I also would argue that 'origin story fatigue' is real. I get impatient with long origin reveals. Just get me into the story and flashback and explain whats going on. I'd rather sit through an exposition episode than a long origins narrative.
Lengthy one-time exposition is perfectly acceptable in tv and film and we do it all the time. I just watched the first episode of Interview with the Vampire and there's a lengthy scene about a previous interview decades before that sets the stage. This isn't the most exciting viewing but allows us to catch up super fast on the story. Its a one-time price to pay that not only sets up the core conflicts but also introduces us to the basics of the main character, the tenor of the show, and the vampire mythologies of this universe.
Novels and such have hundreds of pages to slow burn exposition. In normal script formats you have about 20-25 pages per episode for a 30 min show. Compare that to your average novel at 250-400 pages. Note those 20-25 pages are in screenwriting format, which are closer to 10 or less dense novel pages.
an picture is worth 1000 words
This is different from merely reading it out loud by yourself, which doesn’t give you enough distance.
There's also a Python package on pypi called pyttsx3, which I used to write a very simple command line program to say whatever is on my clipboard.
What I'd really like to do is have a standard "spell/grammar/plothole/tone/etc." critique prompt and have google docs start me from the top and roll down the entire document so we work on one sentence/paragraph at a time and see if I agree with anything pointed out or suggested. Right now there's a lot of copying/pasting, contextless critiquing, but at least claude will be able to read my full document for full context.
And a great way to facilitate this (which I'm surprised the author didn't mention!) is to change the font in your word processor, or to paste your draft into a different text editing program, or anything else that physically transforms how your draft looks.
When you're doing line edits, adding friction between your words and your eyeballs helps you review each sentence more deliberately; otherwise, it's too easy to glide past the same sentences you've already read a dozen times without considering how they actually sound.
Most of the time I write in markdown. I'll have a preview tab open in my editor, or generate a preview.
ETA: the funny thing is I'm a software engineer by trade, have been for 18 years, and I gotta say, there is nothing more satisfying than deleting code. Give me a PR filled with seas of red. I love it. Makes a tonne of sense writing would be the same.
"There is however a way to cheat our way into getting it right the first time: instead of designing a (piece of) program once, we can design it two or three times over, compare, and keep the best approach. Nobody has to know about our embarrassing failures. This takes time and effort, but I believe all significant projects deserve it. That said, I understand why in practice most of the code I see is just a rushed first draft: stopping as soon as it “works” is just too damn tempting." [1]
[1]: https://loup-vaillant.fr/articles/source-of-readability
When you read a text try to make a way too detailed outline for it. In a good text this will still make sense, if you text has jumpy thoughts they will show up in that reverse outline and you can fix them by removing or reshuffling things or by reducing the interuption of the inserted text (by shortening the passage, by rephrasing the sentence, by moving it into a footnote, etc.)
Yes, has more details in it, but does it really matter she spit the gum in the gutter?
I feel the first version, was just the right amount of information, just put in the wrong order.
Then I edit the two together.