One big advantage not mentioned in the article particularly relevant to this audience: git diffs (or your VCS of choice). One sentence per line means diffs will operate per-sentence, rather than per-paragraph. This way the diff can capture the restructuring of the paragraph (adding/removing/replacing a sentence), which gives much more insight than swapping out the paragraph wholesale. It also means minor changes (e.g…
Writing one sentence per line
221–230 of 307 posts
Re: Writing one sentence per line
#222Earlier quoted context omitted.
Five word sentences are fine. The first paragraph is not; the content itself is dull. Do it with useful sentences.
The semicolon is doing a lot of heavy lifting in that sentence. That makes your example 5-10-5 words instead of 5-5-5-5. Try using a period instead of semicolon and hear how it sounds.
Re: Writing one sentence per line
#223Re: Writing one sentence per line
#224This is awful. It’s the LinkedIn writing style and I can’t look at it without being reminded of all the shitposting that “thought readers” do. Thoughts?
My criticism is that nearly the whole page is the comment section. The article itself is very short--pasted into an editor, ~200 words excluding titles. Perhaps putting every sentence on its own line also inflates an author's sense of how long their article is.
Re: Writing one sentence per line
#225[0] https://www.amazon.com/10-Solution-Ken-Rand-ebook/dp/B07FC7G...
[1] https://www.washingtonpost.com/local/bill-walsh-copy-editor-...
Re: Writing one sentence per line
#226Or, with a bit more nuance: Semantic line breaks https://sembr.org/
> 5. A semantic line break SHOULD occur after an independent clause as punctuated by a comma (,), semicolon (;), colon (:), or em dash (—). Uh oh, that’s incompatible with standard em dash usage, which is with no surrounding whitespace. (I’m designing a lightweight markup language of my own, and it’s tempting to special-case an em dash at the end of a line that is not preceded by a space, to join to the next line wit…
Re: Writing one sentence per line
#227It isn't the main point of https://github.com/neilbrown/wiggle , but it can actually diff and merge on a word basis. A git merge driver is fairly easy to set up.
Re: Writing one sentence per line
#228This sentence has five words. Here are five more words. Five-word sentences are fine. But several together become monotonous. Listen to what is happening. The writing is getting boring. The sound of it drones. It’s like a stuck record. The ear demands some variety. Now listen. I vary the sentence length, and I create music. Music. The writing sings. It has a pleasant rhythm, a lilt, a harmony. I use short sentences.…
I'm gonna be honest, my mind got bored in the long sentence and completely skipped like half the words. I think I'm just too used to reading documentation and skipping 50% of the words so I can see how to do something quicker.
Re: Writing one sentence per line
#229Earlier quoted context omitted.
That's about as unnatural for most people as newline per sentence, and has the added risk that you'll accidentally publish like that and it'll look weird. One per line would be _much_ harder to accidentally publish because it's more obvious.
Two spaces between sentences is how I've always typed them, even if it's in HTML or MD or other forms that will condense them into a single space in the final render. The two spaces mark a clear intent to end a sentence instead of a period to punctuate an abbreviation.