Hacker News Reader

That'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.

View on HN

I tend to write prose source code

with line breaks after grammatical units.

I've noticed that since I started doing so,

I've been writing longer paragraphs and sentences,

since the line breaks in the source do for me

what paragraph and sentence breaks do for the reader.

It's something I have to pay attention to.

Writing like this works really well for vim and git as well. It makes it easy to delete/move/edit lines (eg with: d2j), and then in git the diffs are by default formatted nicely and contain only sentences.

Though if you wanted to get fancy you could use other vim movement commands (yank the next 2 sentences), I still think it's easier using lines.

GP was echoing the article's point that writing one sentence per line lets you notice, and vary, your line lengths.

Ah. If that's the case (and I can see how it might be) I misunderstood. Thanks.

Reply on news.ycombinator.com