17 ms·
Writing one sentence per line
- meken 4y agoI like a version of this technique the best for curing writer’s block. When I sit down and try and write the “perfect paragraph”, I get paralyzed. But if I just start barfing out semi-coherent thoughts line by line, I find I’m able to get unblocked, then I can come back and edit.
- throwawayHN378 4y agoBeen doing this forever but not for a particular reaso.
- ngrilly 4y agoI'm doing that almost systemically when writing Markdown for similar reasons to the blog post author.
- michaelmior 4y agoI personally use this approach but mostly because a lot of what I write ends up in a git repository and diffs make way more sense when there is only one sentence per line. I also find things much easier to manipulate in vim when sentences don't span lines.
- pointlessone 4y agoVim has built-in text object for sentences. It supports sentences spanning multiple lines.
- michaelmior 4y agoYes, but I still find it more convenient to have sentences on their own line. Vim's sentence text object does also not always correspond correctly to actual sentences.
- ketzu 4y ago> diffs make way more sense when there is only one sentence per line I did the same thing for some time for papers at university for the same reason. It used to annoy me, because I hate to change for my tools, I rather have my tools support my workflow: There should be a nicer diff for that.
- TheFreim 4y agoYou could write a script which replaces the end of sentences with a new line and use git hooks[0] to run it before every commit. You wouldn't have to write any differently. 0. https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks
- michaelmior 4y agoThis would require accurately detecting the end of the sentence which is not an easy thing to do correctly consistently.
- deleted 4y ago[deleted]
- dubya 4y agoTwo spaces between sentences makes this easy, and should be just as easy a habit as one sentence per line.
- kadoban 4y agoThat'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.
- BeFlatXIII 4y agoTwo 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.
- TremendousJudge 4y agoYeah, same here. If you're going to have any text commited to git, it'll work much better if it's one sentence per line. Not that git is great for prose, but it kinda does the job and I don't need to have a new tool. Hammers, nails.
- kadoban 4y ago> Not that git is great for prose, but it kinda does the job and I don't need to have a new tool. Is there really something better? Git is pretty great in general, and prose doesn't seem like there'd be much room for improvement in tooling. I'm not a writer really though, so maybe I'm missing something?
- ghaff 4y agoAt least with a controlled circle of people who respect that, say, handing off a doc to an editor means they shouldn't make inline changes any longer, collaborative doc editing like Google Docs. As the above implies, you don't have great version control and some of the process management is manual. But it works well for people accustomed to working that way and it's much more familiar for people who don't regularly use git (or use it at all).
- avgcorrection 4y agoI mean, I’m happy that this was not a yet another sysadmin/programmer-as-writer justification (adjusting one’s whole workflow based on the handful of terminal programs that one uses). EDIT: Meaning that I think this kind of justification is more interesting since it is meant to affect the process of writing itself.
- michaelmior 4y agoI won't say I'm not guilty of that too sometimes. Although I don't think it's so bad. If there's a tool that you really like using that can be adapted to work in a variety of scenarios, I can understand the justification. For some of the things I do, there probably are better tools for the job, but if I can make use of existing tools I already know how to use well, even if in a suboptimal way, that might be more worthwhile to me than investing in learning something new.
- avgcorrection 4y agoYep, indeed. Whatever works.
- arathore 4y agoExactly, I mostly write in Latex and one-sentence-per-line makes so much sense for that.
- black_puppydog 4y agoOr, with a bit more nuance: Semantic line breaks https://sembr.org/ https://sembr.org/
- chrismorgan 4y ago> 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 without inserting a space, but I’ve been trying to avoid nuance in rules. But I definitely do want to put line breaks after em dashes sometimes.)
- bloak 4y agoAccording to Wikipedia: "Dashes have been cited as being treated differently in the US and the UK, with the former preferring the use of an em dash with no additional spacing and the latter preferring a spaced en dash." Though I prefer the spaced en dash myself, and I am in the UK, I think there's probably a lot of variation on both sides of the Atlantic.
- lifthrasiir 4y agoIf you are using Markdown you can use an HTML comment—<!-- -->like this. I'm okay with that because there are some edge cases [1] in CommonMark that I absolutely need to use one anyway. [1] https://talk.commonmark.org/t/foo-works-but-foo-fails/2528 https://talk.commonmark.org/t/foo-works-but-foo-fails/2528
- avgcorrection 4y agoA hairline space between em-dashes can be quite visually pleasing (in American writing; British uses full spaces around en-dashes). Like what Medium does. But in that case I would prefer that the source text still has no spaces. Such things can be added in postprocessing.
- nequo 4y ago
- gjvc 4y agojust don't take this as "one sentence per paragraph" unless you want to sound like a used-car salesman.
- ChrisMarshallNY 4y agoI used to do this all the time, when I worked for a Japanese company. They used to translate my emails, "in-place," so this allowed the translators to insert a line of Kanji characters, below each of my lines. It also taught me to be frugal in my content, but you'd never know it, reading my stuff, these days...
- dnpp123 4y agoIt's also one of the first rule I've learned when communicating professionally in Korean. Write the exact same paragraph, one with an EOL between each sentence, one without. Natives always understood the paragraph with EOL. Personally I didn't see any difference but ¯\_(ツ)_/¯ I think it's true all the time, but it shows a lot more when you speak in a language where the grammar is super different from what you're used too.
- Disruptive_Dave 4y agoThis 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. And I use sentences of medium length. And sometimes, when I am certain the reader is rested, I will engage him with a sentence of considerable length, a sentence that burns with energy and builds with all the impetus of a crescendo, the roll of the drums, the crash of the cymbals–sounds that say listen to this, it is important. So I write with a combination of short, medium, and long sentences. Create a sound that pleases the reader’s ear. Don’t just write words. Write music. (Gary Provost)
- pagutierrezn 4y ago"We need to vary the lengths of our sentences. Sometimes short. Sometimes long."
- Ensorceled 4y agoThe comment was a "yes, and" not a "no, but"
- eesmith 4y agoYes, and the hyperlink for "vary the lengths of our sentences" in the linked-to essay goes to another essay, by the same author - https://sive.rs/book/WritingTools https://sive.rs/book/WritingTools - which includes that Gary Provost "tour de force".
- deleted 4y ago[deleted]
- jstummbillig 4y agoThat's beautiful. To be fair, and are we not all about being fair around here, he explicitly states: > Not publishing one sentence per line, no. Write like this for your eyes only. On the other hand, I find it hard to believe that there should be no spillage between how you write and how you publish. For example, I found "How to live" unreadable partly because of what I suspect this style of writing did to the published product.
- oever 4y agoIt's like poetry.
- aasasd 4y agoSuch, errr, ‘giants’ as BBC evidently already adhere to this advice, and others follow in their step. Though I suspect that the motivation is different.
- Angostura 4y agoNo. Their paragraphs rarely extend beyond two sentences in news reports https://www.bbc.co.uk/news/world-europe-61859881 https://www.bbc.co.uk/news/world-europe-61859881 but it does happen.
- honksillet 4y agoI was going to say this. New reporting has denigrated to two sentence paragraphs. It is ridiculous.
- aasasd 4y ago> denigrated I don't think that's the word you're looking for =) (Since we're on the topic of words in this thread.)
- bregma 4y agoThis was the rule in the 1980s when using nroff and it's a habit I developed when using any markup. It's good to know that it's been rediscovered again as newcomers mature in their tool use.
- enriquto 4y agobeautiful html, indeed!
- lqet 4y agoI started doing this mostly for cleaner commits in version control systems. After a while I also noticed it made the writing more concise. It's much easier to spot redundant "filler" sentences.
- cb321 4y agoMost writing style rules are context-dependently apt. The quote by Disruptive_Dave of Gary Provost rings true for artistic writing. Sentence length limits are more helpful for technical writing like papers/documentation, with its many side-details - just as a complexity control. Either way, though, for sentence source formatting, sentences on line boundaries also help version control systems since a diff shows the delta on a per sentence basis. Note that this is slightly different than one per line - it is more integer number of lines per sentence since some are multi-line. Same ethos, though.
- rvnx 4y agoThis is perfect in the era of fast-food media like TikTok or shorts. We don't need long sentences, 140-chars are enough.
- rpastuszak 4y agoI approach this by separating writing from editing. Just keep writing, ignore the typos, self-censorship or formatting and keep moving. So, I've build myself an app to make that easier. Essentially, it's just a more stupid version of a text box. It's free, it's private, and it's meant to put you in the state of flow. I've been using it every day for the past 3 years or so and I know that some people find it useful too, but even if I was the only user, I'd still be quite happy with it, since I suck at sticking with habits :) Check it out! https://enso.sonnet.io https://enso.sonnet.io
- napolux 4y agoI like it!
- edjw 4y agoSimilar idea I made a few years ago. A text editor with no editing allowed and lets you export to Word/MD/HTML for later editing https://first-draft.netlify.app https://first-draft.netlify.app
- rpastuszak 4y agoSweet! If you don't mind sharing, did anyone donate through ko-fi? I think there's still potential in writing tools with decent UX (iA Writer and such) and I know that some people wanted to pay me for Enso, so I'm trying to figure out the best course of action: either charge premium for a premium native app or let the people chip in. Paid products tend to get more valuable feedback.
- edjw 4y agoI just checked and nobody did. I didn't really promote it. Might have helped if I had said what I might do with the money to improve it?
- javajosh 4y ago>I approach this by separating writing from editing. Just keep writing, ignore the typos, self-censorship or formatting and keep moving. You've (re)discovered the old adage: write drunk, edit sober.
- golergka 4y agoIts also very comfortable when you're using vim or vim-emulation plugin in another editor.
- bronikowski 4y agoAs a fan of Proust I feel he already did that but not in the way Derek intended. It's more like "One sentence per page(s) — https://nathanbrixius.wordpress.com/2013/10/30/the-five-longest-proust-sentences/ https://nathanbrixius.wordpress.com/2013/10/30/the-five-long...
- quickthrower2 4y agoIs this why HN joins consecutive lines? This is on line 2. And this is on line 4.
- wccrawford 4y agoNo, that's just how markdown works, and HN uses markdown.
- an_ko 4y agoHN does not use Markdown. Compare HN formatting options https://news.ycombinator.com/formatdoc https://news.ycombinator.com/formatdoc to Markdown https://daringfireball.net/projects/markdown/syntax https://daringfireball.net/projects/markdown/syntax
- wccrawford 4y agoI'll concede that.
- dandare 4y agoMaybe this is the right thread to ask for help: I am looking for resources on the technical aspects of creative writing. Like this post. Or as mentioned below, on using semantic line breaks https://sembr.org/ https://sembr.org/ I am trying to improve my creative writing style but most what I find on Google is about the creative aspect and not about the technical aspect.
- mic47 4y agoAnd it makes git diff pretty.
- nazzacodes 4y ago*more functional
- davnn 4y agoI write one sentence per line as well, but use line wrapping to make it more readable during writing. Reading long sentences on a single line is unpleasant imho. I‘ll try switching from line wrap to full display to get a better picture of the overall structure. If the structure is easy to recognize I would probably prefer a simple model that tells me a good line length for the current line I‘m in, e.g. a simple writing plugin for the editor of choice.
- elfrinjo 4y agoI completely agree. Using one line per sentence (and soemtime more lines when the sentence is longer) makes it way easier to structure the text. Markdown and are perfectly able to fit the text to the device you are reading on. It also makes version control and diffs more usable. However, I can also agree that this style might be not suitable for non-technical writing.
- myfonj 4y agoReading this makes me think it might be generally beneficial to finally convey the semantics of sentence boundaries to the resulting output as well, like some `<p><span>Sentence #1.</span> <span>Sentence #2.</span>` wrappers: it would introduce possibility (for author or user) to break it into lines again or apply any other styling, and might improve interaction (think: select single sentence), or some further processing or contextual styling (think "make all single-sentence paragraphs stand out".) Strange there is no truly "semantic" way to mark-up sub-paragraph chunk of text in HTML; all 'inline' tags are intended for "words" or for including several sentences at once (like emphasis, quote, code, sample, mark, etc.). I have some murky memory I've read some discussion explaining that the concept of "sentence" is quite problematic and in no way universal, but cannot dig it up now. (This comment started as But how are we supposed to sneak our beloved double spaces between sentences in the output now? semi-pun, but after all, this post-processing idea answers it.)
- who-shot-jr 4y agoThis is my sentence. There are many like it, but this one is mine.
- keewee7 4y agoMonths ago I noticed that I was doing this because of a (bad?) coding habit. It meant that my writing was recognizable across multiple reddit and discussion board accounts I don't want to be associated with each other. I stopped Writing One Sentence per Line after that.
- iLoveOncall 4y agoDid you read the article? The author says to write with one sentence per line, not to publish with one sentence per line.
- kstenerud 4y agoWhen I write for myself, it's all over the place. Mostly it's short phrases, unordered lists and the odd diagram, followed by lines of --- to separate thought arenas. All of these are fragments of ideas that I feel will probably be important to the finished piece. Usually about half of them actually are. I just continue writing down thoughts as they occur, any time they happen during the day or during periods of concentration on the piece itself. If the current thought is not an extension of the last thing I wrote, I make a new line and start the new thought. Here's a small section of draft notes for a technical article that I never published: Streaming only for top level args, not deeply nested.... ? - With set of files, need lots of streams of data. -- How to get metadata when ordering not guaranteed? ------------------------------------ Is there a way to evaluate, send data from smallest piece to biggest piece? - Walk the tree, assign weights to branches? If a hierarchy contains multiple big data pieces, how to tell the receiving function? Some method to pump in top level args X items at a time? - 1 item at a time for non-array, x bytes at a time for array ----------------------------------- Every so often I'll draw another line and summarize everything in a way that succinctly discusses what I'm writing about in note form. Then I draw another line and start writing notes again. Eventually, the summary notes start to feel solid in my mind, at which point I turn them into prose and then start embedding my notes between the paragraphs, turning them into sentences only once I feel I know where they should go in the overall piece. Once the notes finally disappear from the prose, I have my first draft.
- wheybags 4y agoSlightly off topic, but a pet peeve of mine is how you don't get a real line break in markdown when you insert a newline. Sometime I want a line break without a vertical apace for a new paragraph, I can't be the only one here! I know I can normally just add a br tag, but that looks nasty when you read it as plain text.
- Jaruzel 4y agoMarkdown allows you to inline HTML, so just use the <BR> tag for a newline. Edit: Oh come now... Editing your post to also say what I replied, then voting me down is poor sportsmanship old chap.
- colejohnson66 4y agoYou can’t downvote direct replies; Only upvote. Meaning any downvotes you’ve received were from others.
- Jaruzel 4y agogood point! (I knew that, honest)
- wheybags 4y agoI wrote that bit about br tags before seeing any replies, sorry :p My sportsmanship is immaculate!
- deleted 4y ago[deleted]
- capableweb 4y agoThat depends on the markdown implementation (like so many features). But most of them implement "two trailing spaces on previous line force line-break" so you can (in most places) do something like this: This is a paragraph with no linebreaks. This is a paragraph with one linebreak but without trailing spaces This is a paragraph with one line break and trailing spaces on previous line That will render correctly on GitHub and other places (meaning, when rendered, the first one has no line-breaks, the second one has no line-breaks but the third one does [select the full third example to see the trailing spaces]) Here is a demo of it in action: https://jbt.github.io/markdown-editor/#dY3RCYAwDET/M8VN4DQuEDW0QWlLUnV9a/0QBCEQuLx7GaM62jAKGwfjEnFqjUgZmyaZTHj1gWj8ASkneUlMe+1xbrsaa7sEeOFZ/N+B2wG6LXg0nJZvvUEoJofm3ftDugA= https://jbt.github.io/markdown-editor/#dY3RCYAwDET/M8VN4DQuE...
- amake 4y ago\(゚Д゚)/ > be me > write one sentence per line > looks like greentext > mfw
- swamp40 4y agoThen they accuse you of reddit spacing.
- longrod 4y agoFor me context is very important. Separating out the sentences, although makes them stand on their own, often sounds discontinuous and jarring like a too long pause. Not to mention how awkward it looks on the page (if double spaced which I prefer). That's not to say it's a bad technique. It might work for some, not for others. For me it doesn't. I have found writing to be much like coding where if you think through the idea properly, writing to the end is not such a big problem. The main hurdles is getting stuck which is often an indicator of a poorly thoughtout idea. The other thing that helps me escape the over-editting issue is putting my words down with as much brevity is possible. The more fluff there is, the harder it is to change. Simpler to read, simpler to edit.
- hansword 4y agoYou might have missed a part of the article, where author says they write single line sentences as 'code', but both Markdown and HTML automatically turn concescutive sentences into paragraphs, unless you (using a blank line or <p>) explicitly end a paragraph. > Not publishing one sentence per line, no. Write like this for your eyes only. (Edit: added quote from article)
- supersrdjan 4y agoOne sentence per line can paralyze your writing. It invites you to over-scrutinize each line and lose sight of the whole. It's a view that's better suited for analysis than synthesis. So it's better for editing than composing.
- trasz 4y agoThis is how man pages are written, and in the long run it’s really convenient. I’m guessing that’s also why it recently become the rule for FreeBSD documentation, after migrating from DocBook to AsciiDoc.
- generalpf 4y agoIs this what inspires LinkedIn engagement hackers?
- AndyJado 4y ago[dead]
- elchin 4y agoLaTeX does the same as Markdown and HTML - I used to do this when I was in academia.
- btrettel 4y agoSome previous discussion of this writing/coding style (though not of this particular page, which didn't go online until today): https://news.ycombinator.com/item?id=31695393 https://news.ycombinator.com/item?id=31695393 https://rhodesmill.org/brandon/2012/one-sentence-per-line/ https://rhodesmill.org/brandon/2012/one-sentence-per-line/ https://news.ycombinator.com/item?id=4642395 https://news.ycombinator.com/item?id=4642395 http://www.uvm.edu/pdodds/writings/2015-05-13better-writing-editing-thinking-with-line-breaks/ http://www.uvm.edu/pdodds/writings/2015-05-13better-writing-...
- globular-toast 4y agoThis is not a bad idea. Any decent toolchain will support rendering as paragraphs, including LaTeX. Another advantage not stated is version control and diffs work much better. You do have to put up with long lines, but most editors support wrapping long lines for display purposes. I wish I had done this while writing my PhD thesis.
- nojs 4y ago> Not publishing one sentence per line, no. Write like this for your eyes only. Many news outlets now use this as standard for publishing. Random example: every article at https://www.abc.net.au/ https://www.abc.net.au/ I challenge you to find a (non-quote) paragraph with more than one sentence!
- II2II 4y agoHowever, the intent is different. The author is suggesting a general purpose method to facilitate a more engaging writing style that can be used even if the product contains paragraphs of multiple sentences. News outlets use it to facilitate the conveying of information to the reader. (Incidentally, it is not too hard to find multi-sentence paragraphs in news stories, though it is rare to find anything exceeding three sentences.)
- edpichler 4y agoIt is an advice for Internet only, right?
- erellsworth 4y agoTangentially related: "Omit needless words." -William Strunk, The Elements of Style Highly recommended book for anyone who wants to be a more effective writer.
- mattbee 4y agoAs a writing manual, I am also a big fan of "First You Write a Sentence" by Joe Moran.
- eesmith 4y agoHave you read any of the criticism of the book? Its Wikipedia entry quotes Pullum: > The book's toxic mix of purism, atavism, and personal eccentricity is not underpinned by a proper grounding in English grammar. It is often so misguided that the authors appear not to notice their own egregious flouting of its own rules ... It's sad. Several generations of college students learned their grammar from the uninformed bossiness of Strunk and White, and the result is a nation of educated people who know they feel vaguely anxious and insecure whenever they write however or than me or was or which, but can't tell you why. (See also "50 Years of Stupid Grammar Advice" at, eg, https://www.cambridge.org/core/services/aop-file-manager/file/5bd889926431f1de07115e6e/209-50-Years-of-stupid-grammar-advice.pdf https://www.cambridge.org/core/services/aop-file-manager/fil... . Language Log recommends https://www.google.com/search?hl=en&q=Strunk+site%3Ahttp%3A%2F%2Fitre.cis.upenn.edu%2F%7Emyl%2Flanguagelog&btnG=Google+Search&gws_rd=ssl https://www.google.com/search?hl=en&q=Strunk+site%3Ahttp%3A%... as a way to find further criticism from them.) For "Omit needless words", a problem is identifying what "needless" means. Quoting http://itre.cis.upenn.edu/~myl/languagelog/archives/004552.html http://itre.cis.upenn.edu/~myl/languagelog/archives/004552.h...: > Whenever you see an appeal to ONW, you should wonder what people are doing with those "needless" words. Most of the time, those extra words are serving some function that conflicts with brevity; they're doing some work. There are also examples how that phrase (likely) caused people to believe that if a word can be omitted then in must be ommitted, like http://itre.cis.upenn.edu/~myl/languagelog/archives/004176.html http://itre.cis.upenn.edu/~myl/languagelog/archives/004176.h... and http://itre.cis.upenn.edu/~myl/languagelog/archives/000994.html http://itre.cis.upenn.edu/~myl/languagelog/archives/000994.h... . Or how in White's own writings he "sometimes throws in a few extra words just for the sheer resonant fun of it" - http://itre.cis.upenn.edu/~myl/languagelog/archives/001904.html http://itre.cis.upenn.edu/~myl/languagelog/archives/001904.h... . FWIW, I think "don't be too wordy" is more accurate and less likely to be misunderstood than "omit needless words", and one character shorter. (Personally, I still recall my utter confusion in 11th grade English trying to figure what "passive" meant when told to avoid it. Turns out three of the four examples of passive in "The Elements of Style" ... aren't passive! And yes, I got marked off for using what may- or may-not have been the passive.)
- mad44 4y agoI had copied this Emacs macro just for doing that. ;; one sentence per line (defun wrap-at-sentences () "Fills the current paragraph, but starts each sentence on a new line." (interactive) (save-excursion ;; Select the entire paragraph. (mark-paragraph) ;; Move to the start of the paragraph. (goto-char (region-beginning)) ;; Record the location of the end of the paragraph. (setq end-of-paragraph (region-end)) ;; Wrap lines with 'hard' newlines (i.e., real line breaks). (let ((use-hard-newlines 't)) ;; Loop over each sentence in the paragraph. (while (< (point) end-of-paragraph) ;; Determine the region spanned by the sentence. (setq start-of-sentence (point)) (forward-sentence) ;; Wrap the sentence with hard newlines. (fill-region start-of-sentence (point)) ;; Delete the whitespace following the period, if any. (while (char-equal (char-syntax (preceding-char)) ?\s) (delete-char -1)) ;; Insert a newline before the next sentence. (insert "\n"))))) (global-set-key (kbd "M-j") 'wrap-at-sentences)
- capableweb 4y agoIronically, this snippet seems to be a bit too much wrapped! You need to have a empty line between each line on HN for it to format correctly. If you also ident it by four space, it gets marked as code in the markup.
- yvdriess 4y agoI just love the irony that one needs to manually insert newlines to copy over code to automate inserting newlines.
- mad44 4y agoFine, here you go, with the line breaks ;; one sentence per line (defun wrap-at-sentences () "Fills the current paragraph, but starts each sentence on a new line." (interactive) (save-excursion ;; Select the entire paragraph. (mark-paragraph) ;; Move to the start of the paragraph. (goto-char (region-beginning)) ;; Record the location of the end of the paragraph. (setq end-of-paragraph (region-end)) ;; Wrap lines with 'hard' newlines (i.e., real line breaks). (let ((use-hard-newlines 't)) ;; Loop over each sentence in the paragraph. (while (< (point) end-of-paragraph) ;; Determine the region spanned by the sentence. (setq start-of-sentence (point)) (forward-sentence) ;; Wrap the sentence with hard newlines. (fill-region start-of-sentence (point)) ;; Delete the whitespace following the period, if any. (while (char-equal (char-syntax (preceding-char)) ?\s) (delete-char -1)) ;; Insert a newline before the next sentence. (insert "\n"))))) (global-set-key (kbd "M-j") 'wrap-at-sentences)
- drewg123 4y agoJust please, for the love of god, don't do it in slack. Nothing annoys me more than a colleague writing a long slack message when I'm AFK, and having my watch buzz like an angry bee when they hit one carriage return (and send a new slack message) every 10 seconds.
- Beltalowda 4y agoYou should really be angry at Slack and not your colleagues. There are loads of ways to prevent this like sending at most one alert per user per minute (if message is unread). It's not rocket science. Most times when loads of people are "doing it wrong" then it's the technology that is at fault, and not the people.
- DawsonBruce 4y agoOver the past year I’ve disabled all Slack notifications and the result is increased focus while I’m writing some code or an email. All the messages will be queued up regardless if I’m being notified (and disrupted) often. Perhaps give it a try!
- drewg123 4y agoYes, I'm angry at slack. No other messaging system I've used does this..
- eCa 4y agoPersonally, I have mapped ’send’ to cmd+enter, to avoid accidentally sending too soon. Also, to make it behave similarly within a code block as without.
- secondcoming 4y agoJoke's on you for connecting your watch to Slack.
- drewg123 4y agoSadly, I have no choice. I have a Garmin connected to an iPhone. Even when I disable most notifications for an app, it will still hit my watch. On Android, I could filter out which apps could notify the watch, on ios, it seems Garmin has not been able to do that.
- vishkk 4y ago“Words are not forms of a single word. In the sum of the parts, there are only the parts. The world must be measured by eye.” - Wallace Stevens
- bertil 4y agoI remember struggling to write essays when I was in highschool. Well, I was fine, but my teachers insisted it was long-winded gibberish. Concerned, my grand’mother told me: “Ask Sonia” I knew she was her friend, and they liked to argue a lot, but I was a bit confused by the advice. It turns out, editing was Sonia’s job: she was the head reader at a very prestigious publishing house, meaning she was giving notes and feedback to very famous authors, including four Nobel Prize laureates. You kind of have to know what you are doing when you are sending a manuscript full of red in the margins and the person can respond “I’ve got a Nobel Prize and you don’t.” She definitely had the icey stare to match. Oddly, her advice was incredibly simple, and fitted in two very short pieces: * Subject, Verb, Complement –– in that order. If you see two verbs, but a period between them. * Things are confusing if you don’t put them in order: start by the beginning, find the widest piece of context that explain the rest. I don’t apply her rules every time, but for every technical document, every time I’ve tried, it’s been night and day. That typographic argument is really resonating with me.
- drivers99 4y ago> find the widest piece of context that explain the rest. Sounds interesting. Can you explain this?
- bertil 4y agoFrench, especially academic writing, can have a lot of subordinate clauses: > I asked the person who was standing there. It has even more oratory precautions: > We can argue that this result, that was seemingly proven wrong by a previous analysis, appear to be a consequence of a previous attempt that was investigated by my esteemed colleagues, who have looked into the author and found out that they … If you want to split between each verb as they are, you end up with sentences that are in the wrong order: > I asked a person. That person was standing there. > We can argue that this result appear to be a consequence of a previous attempt. This result was seemingly proven wrong by a previous analysis. The attempt was investigated by my esteemed colleagues. My colleagues have looked into the author. They found out that the author… So you are better off by thinking: what comes first? The person was standing there _before_ I asked, and I asked them because they were standing, so that information should come first: > A person was standing there. I asked them. Further, most actions in a chain of preposition explain a decision: those should come first. > This result was surprising. Sceptics wanted to verify it. Their investigation concluded that the result was wrong. My colleagues wanted to know more. They investigated the authors of the result. They found out… The outcome is a bit drier. The benefit is that if one sentence is longer, or an adjective inverted, or a complement put at the begining of the sentence, it’s more striking. That helps attracting attention to what matters, selectively. For academic writing, you don’t need as many oratory precautions because you can report other findings without having to validate them as yours: you present them all as facts on equal footing. If you agree, it’s implied from the lack of criticism. If you disagree, it’s on you to prove why _after_ presenting the work fairly. For that, you have to include the key aspect to support you criticism in your first presentation. I can also give the impression that you are just moving forward without a clear goal: “This happened, in particular then this happened, then this reacted…” which is why you want to summarise your point early: people will see the arguement getting closer to its goal, knowing what that goal is.
- Hendrikto 4y agoThis reads like it was written by a third-grader. Accessible? Maybe. Enjoyable? Not in my book. As a German speaker, I feel like English prose is already extremely biased towards short sentences. This makes some sense, as German has much more grammar to make these sentences readable and unambiguous. At some point, I feel like making sentences even shorter does not aid the readability, but rather stands in its way.
- xwdv 4y agoSentences are just a tool for exchanging an idea. The actual sentence doesn’t matter, only the idea.
- thejohnconway 4y agoThe article isn't advocating making sentences shorter. It is using short sentences, but that is not what is being said.
- avgcorrection 4y agoIf you want five-line sentences with plenty of dashes and semicolons then the American Humanities still has got you covered.
- mbg117 4y agoThis article had more to do with the visual separation of sentences, so they're easier to inspect at a glance, and not so much how small they are. Not necessarily the containment of each sentence to a single line, but a new line between each sentence to maintain separation.
- hammock 4y agoMost news articles are written one sentence per line. You might not have ever realized this fact because the character length of a typical line is so short, both in a columnar newspaper and on an ad-ridden website.
- kwelstr 4y agoJames Joyce best advice? :-O
- stewfortier 4y agoI think the spirit of this advice translates well to publishing style, too. I get intimidated when I see big blocks of text. But take that same, intimidating block and thoughtfully break it into short, punchier paragraphs and I'm in. Shorter paragraphs make it easier for me to skim and get a sense of where something is going. They also give me more chances to pause, catch my breath, and internalize what I'm reading. This is harder for me to do in a big block of text where I'm afraid I'll lose my place if I divert my attention.
- pkdpic 4y agoOk. I love it. This could change everything. Future historians may thank us. Seriously.
- bee_rider 4y agoIt is the easy way to do things when writing LaTeX in vim.
- 3qz 4y agoThis 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?
- iainctduncan 4y agoDid you even read to the second paragraph of the article??? He says specifically in the source... not the render.
- jyriand 4y agoI don't think it's awful. As he says you shouldn't publish your text that way. In editing phase you will merge one line sentences into paragraphs.
- zaps 4y agoAgree
- mirrorlake 4y agoMy 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.
- dchest 4y agoWhy do you need a longer article for such a simple idea?
- matwood 4y agoI'm not really a fan of 1 line per sentence as the default, but agree with more breaks. Also know your audience. My default structure is: - Ask for what I want/why did I sent this email. - Explanation why using logical breaks. Which usually means I write my email, take the last line and make it first. If I'm emailing a technical colleague I'll include more details. CEO, 1 line bullet points.
- dilap 4y agoIf that's too much trouble, just write your essay as a series of tweets. Similar focussing effect. (And part of why I think the essay-as-tweet thread is so popular.)
- jillesvangurp 4y agoGood advice. There are a few nice tools out there to support technical writing. I think one of them was featured on HN a few days ago: vale. This is a tool that allows for applying simple regular expression based rules to enforce style rules. The idea is that you can tune this to your needs and cover all sorts of stylistic rules. For example, gender neutrality might be a desirable thing in the documentation for some tech companies and you can get it to flag things that are clearly not gender neutral. Another thing worth mentioning is Jetbrains Grazie Professional (warning it's different from the normal grazie plugin, which is confusing), which actually integrates vale and can be used as a plugin for editing both code comments and markdown files in Intellij and other Jetbrains IDEs. In general, treating text like you would treat programming code as a thing that has rules that can be figured out and enforced is a good mindset. I learned to write coherent text while doing my Ph. D. a long time ago. At some point I figured out that anything I'm doing consistently wrong, I can just learn to do consistently right. I just need to be open for criticism and figure out why something is wrong/not ideal. You kind of learn to look for things that you've done wrong before in your own text and then you fix it. A lot of these rules aren't rocket science. You just need to know about them. There's a whole grey area between grammatically correct and stylistically pleasing/acceptable. Having tools point out things that are likely problematic helps.
- clord 4y agoThis is my primary objection to using 80 columns everywhere. Markdown specifically is a painful place to require it, but also latex and HTML. For source code, 80-col works out ok most of the time since "sentences" are relatively short, but even there I prefer to use more semantic line breaks when the style guide or formatting tool does not omit them.
- innocentoldguy 4y agoI write this way in Asciidoc, with a single line break between sentences and two line breaks between paragraphs, since it automatically compiles into normal paragraphs when I generate PDFs or Word documents. It makes editing so much easier.
- personlurking 4y agoReminds me a bit of Jordan Peterson's advice to rewrite every sentence until it's the best it can be, and then repeat that with each paragraph. His son recently released Essay, a tool to help write better, in the sense mentioned above. https://essay.app https://essay.app
- hanifc 4y agoThis entire comment was what came to mind as soon as I opened the post. Glad I found it here. His process is outlined here: https://medium.com/practicecomesfirst/dr-jordan-b-petersons-10-step-guide-to-clearer-thinking-through-essay-writing-1ab79a94937 https://medium.com/practicecomesfirst/dr-jordan-b-petersons-... I believe the app is a tool to help you learn, practice, and internalize that process.
- swamp40 4y agoI have to do this in my emails. Most people just ignore the second and third sentences in a paragraph. No idea why, drives me crazy - but this does help. You can tell they don't read them because they ask questions that were answered in them.
- warmwaffles 4y agoWhy would you do that in your emails? /s
- ghaff 4y ago>No idea why Because that tends to be how people skim. If the first sentence of a paragraph doesn't catch their attention in some way, they subconsciously assume that the rest of the paragraph (which is presumably related) doesn't need to be read.
- hinkley 4y agoWhich is why “don’t bury the lede” is such important advice. Also please rehearse what you would say to your family if you got into a car wreck and they wanted to check you out at the hospital versus “mom is going into surgery for massive hemorrhaging.” “Hey son, we’re okay, but we got into a bad fender bender and we’re getting checked out at Hoskin’s Hospital. The car is dead so can you come pick us up, maybe bring X and Y and have your sister check on the cats?” Is a way shorter moment of sheer terror than switching around the sentence fragments at the beginning. Also if you’re a boss having an unscheduled meeting with someone, stalling the agenda is just torturing the other person.
- Groxx 4y agoThis is all also useful advice for helping people deal with notifications for work. They might see "@xyz can help you with this..." and miss "... when they have time next week". Help people triage. Make the urgency clear in the first couple words. Don't just send "hi" and then wait for a response, nor "X is down" when someone else is already on it and you're just giving them an FYI.
- gist 4y ago> My advice to anyone who writes: Try writing one sentence per line. I’ve been doing it for twenty years, and it improved my writing more than anything else. Who is the judge of 'it improved my writing more than anything else'? What was the 'anything else' for that matter. This is a particular writing style just like Aaron Sorkin has a particular style. Some people like that style to others it's annoying. https://thescriptlab.com/features/10569-5-secrets-to-aaron-sorkins-dialogue/ https://thescriptlab.com/features/10569-5-secrets-to-aaron-s... > We sometimes write sentences that don’t need to exist. Hidden in a paragraph, we might not notice. Standing on their own, we notice. Delete any sentence not worthy of its own line. If you proofread and review what you write why would you not notice?
- pessimizer 4y agoThis isn't suggesting that the things that you publish be one sentence per line. It's suggesting that you write one sentence per line, polish the individual sentences (and question their right to exist at all) then edit them into paragraphs. You might have assumed this assume this by noticing the fact that the article has more than one sentence per line. > Who is the judge of 'it improved my writing more than anything else'? Who do you think? Who wrote the article? The word 'my' might be a hint. > What was the 'anything else' for that matter. Would you give him permission to describe one practice he adopted while writing without describing every single step he's made in learning how to write since he was a child?
- gist 4y ago> Who do you think? Who wrote the article? The word 'my' might be a hint. I am challenging how someone arrives at that conclusion if they are the judge (which seems implied). Sivers gives nothing at all to indicate - not even anecdotes - as backup for the improvement. His statement is general and broad. Let's say he was instead describing writing he did for school or for work. So before he applied his technique he was rated or judged a certain way (grades, reviews). Then he started to use the technique he describes. He then gets better grades or reviews. In that case he concludes 'it improved my writing more than anything else' (and I might still ask 'what are the other things you tried that did not work'. But in this case all he says (again) is a very broad and not in any way backed up 'it improved my writing'. And he claims 'advice to anyone who writes' he can't be serious using 'anyone' in that 'polished' sentence other than to get people worked up over a blog post and talking about it (which to be clear is a technique that bloggers use) > Would you give him permission to describe one practice he adopted while writing without describing every single step he's made in learning how to write since he was a child? People read what others have written and critique. My guess is that if he read my comment he might think that someone thought a certain thing and wonder and then maybe he would learn and/or make an adjustment. Not the reason I made my comment but there is nothing that indicates he should not be criticized or that others can't learn from the statements that I made whether they agree or not with what I said. > It's suggesting that you write one sentence per line, polish the individual sentences Again he is not even indicating when his technique matters. I write every day (for sales) I get very good results (judged by replies and results). In my case I don't have to polish every sentence I write enough and have enough feedback that I find that sometimes you don't even want to care that much because that in itself (in certain situations) telegraphs something. You don't think starting a post with this is a bit to broad: "My advice to anyone who writes: Try writing one sentence per line." Seems very clear to me 'advice to anyone who writes' seriously 'anyone'?
- nunez 4y agothis is actually really good advice. shorter paragraphs force you to be concise, and concise is really good in short-attention-span mediums like reddit or email.
- lo5 4y agoRelated: Cormac McCarthy’s tips on how to write a great science paper[1] > Limit each paragraph to a single message. A single sentence can be a paragraph. [...] > Keep sentences short, simply constructed and direct. [...] [1] https://www.nature.com/articles/d41586-019-02918-5 https://www.nature.com/articles/d41586-019-02918-5
- mixedmath 4y agoI write a lot of LaTeX and articles. I sort of do this, except that I also really want reasonable line lengths. Each sentence starts on its own line, but I also hard wrap at 80 characters. I have a completely different set of editing tidbits for writing equations.
- MengerSponge 4y agoThis is a good habit if you write LaTeX documents, particularly with collaborators. It's much easier to diff a file where each sentence has its own line!
- pauljonas 4y agoJose Saramago would hate this.
- jvanderbot 4y agoIf you've ever had LaTeX docs in version control, you'll quickly appreciate this approach as well, since VCS is much more sane when dealing with lines.
- abhayhegde 4y agoSimilar advice was given by a famous VC, Tomasz Tunguz, a few years ago: https://tomtunguz.com/writing-separate-lines/ https://tomtunguz.com/writing-separate-lines/
- Mageek 4y agoI absolutely love doing this. I often write in LaTeX, where new lines don’t effect the typeset output. It is so much easier to see git diffs, comment sentences out, move sentences, identify a sentence by its line number, etc. as well.
- cjsawyer 4y agoI love the irony of using a two sentence opening paragraph to sing the praises of not using paragraphs. Good advice though ;)
- planetsprite 4y agotech bloggers discover greentexting
- luhn 4y agoOne 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. typo fixes) will only add+delete a single sentence, making it much easier to identify what has actually changed from one commit to the next. I take this a step further and will often split out a single sentence into a clause per line, but this is a judgement call rather than a hard and fast rule.
- majormajor 4y agoMany GUI diff tools will do this neatly regardless of whitespace, FWIW, so this hasn't been a motivator for me for code or text.
- hinkley 4y agoI think we need to start changing this. In an era of language servers, perhaps our diff tools should be semantic instead of line based. I get so tired of seeing diffs where I add a function and the diff shows that I added it inside the previous function instead of between them, because it starts the diff one line too early.
- dahfizz 4y agoYes! I find `git diff` to be the most annoying thing about git. I can be pretty forgiving of the clunky UX, but the diff output is just wrong. People often say of git, "The porcelain is bad but the plumbing is good". The opposite is true for digging, IMO.
- sangnoir 4y agoFortunately, git permits the use of external difftools. One can easily configure git to use their preferred semantic diff tool and git wouldn't even care. The plumbing is excellent.
- danielvaughn 4y agoI always do this for markdown, makes it waaay easier to edit, reason about, cut, etc.
- dang 4y agoI tell founders not to write like this, at least for HN, and I edit their launch posts when they do (https://news.ycombinator.com/launches https://news.ycombinator.com/launches), because it reads like a sales letter. But the OP is saying that it's useful to make the sausage that way, not sell it that way, which is a different point.
- dws 4y agoElsewhere, https://sive.rs/book/ShortSentences https://sive.rs/book/ShortSentences, Sivers recommends "Several Short Sentences About Writing", which is a perspective on writing that I'd not seen before. A useful read if you want to practice his present advice.
- joegahona 4y agoI read Ken Rand's "10% Solution"[0] in ~2001 on the recommendation of longtime Washington Post copy chief Bill Walsh, who died a few years ago[1]. I can't believe how much of its advice has stuck with me and how much it has helped me. Highly recommended for anyone who wants to optimize their writing. [0] https://www.amazon.com/10-Solution-Ken-Rand-ebook/dp/B07FC7GQWJ/ref=tmm_kin_swatch_0?_encoding=UTF8&qid=&sr= https://www.amazon.com/10-Solution-Ken-Rand-ebook/dp/B07FC7G... [1] https://www.washingtonpost.com/local/bill-walsh-copy-editor-and-witty-authority-on-language-dies-at-55/2017/03/15/6bf9dea4-002e-11e7-8ebe-6e0dbe4f2bca_story.html https://www.washingtonpost.com/local/bill-walsh-copy-editor-...
- wnoise 4y agoMany comments have mentioned both the benefits to diffing, and various --word-diff options. Unfortunately word-merge tools are harder to find. You can of course use smudge/clean filters to unwrap and rewrap text, but those are quite fiddly to set up and fragile in practice. It isn't the main point of https://github.com/neilbrown/wiggle 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.
- preseinger 4y agoOne sentence per line makes prose feel sanctimonious, even self-aggrandizing. I find this dude's writing un-readable for exactly this reason. All of his articles are like HTML versions of the Ducks Go Quack TED Talk [0]. I just roll my eyes. [0] https://www.youtube.com/watch?v=tom6_ceTu9s https://www.youtube.com/watch?v=tom6_ceTu9s
- kuhzaam 4y agoIn his defense, he is saying to write "one sentence per line" only _while_ you are writing/editing. He says this is "for your eyes only", and that you'll recombine into paragraphs afterwards. I think the idea is that, if your sentence can stand up to the added scrutiny you'll give it while seeing it sitting all alone, then it is worth keeping. Otherwise it is a wasteful sentence. Anyway, I do agree that the actual "one sentence per line" prose that is so pervasive on places like LinkedIn is awful.
- Semiapies 4y agoAt this point, I think it's wasted breath to try to respond to the people who skim over articles without comprehension (or who don't appear to read the articles at all) and who instead just respond to the title.
- preseinger 4y agoI understand the difference between one line per sentence at the source level, and at the presentation layer. As far as I can tell, articles on sivers.org demonstrate both.
- Enginerrrd 4y agoI think the advice is still useful for editing. Personally, I'd add the extra step of re-consolidating the sentences into paragraphs after going through this editing phase though. That said, I do a lot of technical writing and I often find paragraphs with fewer sentences are my better written paragraphs.
- __MatrixMan__ 4y agoIf what you're writing gets rendered as markdown (i.e. a readme on github), you can actually publish as one-sentence-per-line, because the markdown parser will make them into a paragraph for you.
- mjcohen 4y agoThe mathematician Lillian R. Lieber wrote a number of expository books in which the text had one phrase per line. I found this extremely easy to read, and I write my LaTex this way, which makes it very easy to edit. Here is what the previous paragraph would look like in her style: The mathematician Lillian R. Lieber wrote a number of expository books in which the text had one phrase per line. I found this extremely easy to read, and I write my LaTex this way, which makes it very easy to edit. I highly recommend the wikipedia article about her and its references: https://en.wikipedia.org/wiki/Lillian_Rosanoff_Lieber#Unusual_typography https://en.wikipedia.org/wiki/Lillian_Rosanoff_Lieber#Unusua...
- sequoia 4y agoI'm surprised no one has mentioned ventilated prose, which is like this but even moreso: https://vanemden.wordpress.com/2009/01/01/ventilated-prose/ https://vanemden.wordpress.com/2009/01/01/ventilated-prose/
- HeavyStorm 4y agoI cannot disagree more profoundly with the author. Write in a very different way from which you read? From how texts are formatted in general?
- qudat 4y agoHis rationale is also why I enjoy writing in list format. https://lists.sh https://lists.sh is great for one sentences per line writing style.
- iainctduncan 4y agoAm I the only one thinking this thread should be immortalized as the ultimate example of how poorly HN readers read things before shit-posting about articles? Sigh. A) He says in the SOURCE not the published, in literally the third paragraph. B) Count the damned sentences in the first handful of paragraphs. 2,3,3,1,4. He's clearly not saying you should do the stupid one paragraph per sentence nonsense in the published article. This is a great idea for those of us who like writing prose in vim. Will adopt!
- danw1979 4y agoI love these small but significant improvements that are kind of obvious but were hidden in plain sight. For years I didn’t even consider there was an alternive to writing in paragraphs, despite using git and markdown daily.