7 ms·
Don't make your readers hold parts of the sentence in their head. Reorder or split sentences until it can be avoided. In other words, use a really small buffer.
by nicbou 6y ago
Don't make your readers hold parts of the sentence in their head. Reorder or split sentences until it can be avoided. In other words, use a really small buffer.
"You must fill form 331 unless you are over 60 years old, in which case you must fill form 445."
"You must fill form 331. If you are over 60 years old, you must fill 445 instead."
"If you are over 60 years old, you must fill form 445. Otherwise, you must fill form 331."
You might have noticed that the last version is an if-else statement.
- dragonwriter 6y agoYour last one requires keeping the first clause of the first sentence in your head; just because you've split sentences doesn't mean you've avoided that, because “otherwise” imports the conditional in the previous sentence by reference and then inverts it. To actually avoid requiring the reader to keep sentence parts in their head, use if-then or do-if constructs, but not if-then-else constructs. “Complete form 445 if you are over 60 years old. Complete form 331 if you are 60 years old or younger.”
- nicbou 6y agoI disagree. Putting the "if" clause first means you can skip this sentence. In other words, the if-sentences are guard clauses to the default option (fill form 331). In other words, it's not really an if-else block, but just an if statement before the default scenario. Almost everyone has to fill form 331. I think the sentence structure you suggest would quickly make a longer text tedious to read. I have experimented with that sentence format, and it added a lot of text, but not a lot of clarity. I also think that putting the if statement at the end makes little sense, just like when reading code.
- bloak 6y agoThat's a bad example of how to express age limits. If I've just had my 60th birthday, or perhaps today is my birthday, which applies, or do I have to fill in both forms? Also, is it my age at the time I sign the form, or my age at the time the form is received, that matters? Arguably that's a problem with the rule itself rather than how it's expressed. It's better if you can write something like: "If you were born before 6 April 1960 ... otherwise ...". Note that "after 6 Apr 1960" is arguably more ambiguous than "before 6 Apr 1960" because there's a slight risk that someone could interpret "6 Apr 1960" as meaning 1960-04-06 00:00:00. This problem is vaguely related to the insurance policy renewals that leave a one-minute gap between the old policy and the new policy, and even more vaguely related to the ambiguity of "midnight on the next day".
- touisteur 6y agoOh man I'm having day nightmare flashbacks about the time I spent days parsing some well-meant European Energy-Saving directive and figuring out whether we could sell a PC with a fixed-frequency CPU, and all power- and energy-saving features disabled (latency concerns). Ouch... There were some official and unofficial logic diagrams and they made things even worse. Lexicon was pretty vague, use-cases too, exceptions too... and you end up writing some kind of justification for you being one of the special cases and praying it's OK. And it wasn't even the worst normative document I've ever read. It was clear about the spirit of the directive... Imprecise language to allow flexibility and 'let the judges decide'... I'm not sure I'm comfortable with common-law-inspired regulation. Not sure how to do this better though.
- deleted 6y ago[deleted]
- dragonwriter 6y ago> It's better if you can write something like: "If you were born before 6 April 1960 ... otherwise ...". Note that "after 6 Apr 1960" is arguably more ambiguous than "before 6 Apr 1960" because there's a slight risk that someone could interpret "6 Apr 1960" as meaning 1960-04-06 00:00:00. I strongly prefer pairing “before” and “on or after” (or “on or before” with “after”) when it comes to dates. “On <date>” is widely and conventionally understood to encompass the entire day, and it seems to make it far less likely than with after/before alone with “otherwise” that people will trip up over boundary conditions. But the right phrasing is highly sensitive to the context and the underlying rule; if it's an age based rule and you have fixed text that doesn't dynamically adjust by dates you can't use date-based language even if it would be clearer.
- omnicognate 6y agoOverflowing that buffer really does feel like a stack overflow, too. Your whole mental state just suddenly disappears in a puff of smoke. This resplendent sentence in the Vulkan spec did it to me the other day: The layout of subresources of images on other logical devices that are bound to VkDeviceMemory objects associated with the same underlying memory resources as external memory objects on the lost device becomes VK_IMAGE_LAYOUT_UNDEFINED. I got about half way through and suddenly discovered I didn't know where I was, what year it was or my name.
- nicbou 6y agoThis is how I felt while reading philosophy essays. I'm not even sure half of those are even saying anything.
- vidarh 6y agoA lot of philosophy essays are written as part of the writer being in the process of trying to figure things out for themselves, without quite having gotten there yet.
- formerly_proven 6y agoIt really shows, just like docs written by someone who hasn't actually understood what they're writing about yet.
- mlvljr 6y agoOr those Medium blogs.
- darkerside 6y agoThis is why second drafts exist
- brain5ide 6y agoWe had this joke. A meeting of faculty heads is taking place. The topic - funding. The chairman says: "Hey, physicists, why are you so expensive? You need all those gadgets and materials to perform your experiments. Look at the mathematicians. All they need to produce a research paper are a box of paper, a box of pencils, and a trash can." "We don't even need trash cans, sir." announces the dean of Philosophy.
- inopinatus 6y agoExperienced UX practitioners will immediately note that a surprisingly large proportion of users don't actually know how old they are; furthermore, of those that do, another significant segment will (intentionally or otherwise) mis-state their age, date of birth etc. This problem is further exacerbated by the wide variety of temporal arithmetic possibilities any such workflow might adopt. The solution is to either combine the forms, or (in an interactive context) ask the user if they were born before 1960, then give them the right form.
- nske 6y ago> a surprisingly large proportion of users don't actually know how old they are How did they manage this? I've tried every way I can think of forgetting my age, to no avail -the bastard number is always there :)
- nicbou 6y agoI'm in my late twenties and sometimes I need to pause, a bit like dealing with left/right or east/west.
- alexchamberlain 6y agoI may forget my age, but I can't forget I'm now over 30.
- smichel17 6y agoI'm in my twenties. Sometimes I forget my age. Only ever by one year -- I just don't remember if my birthday passed or not. Kind of like in January when write oit today's date and accidentally use the previous year. After a few mistakes, your brain adjusts and you start using the right one. Same thing for my age, except that I don't actually think about my age very often; it hasn't mattered much since I passed 21.
- sethammons 6y agoA colleague of a old friend would recall your birth year (and date?) to know your age. It is a value about you that doesn’t change and then you can derive the age. I’ve started doing similar now. I don’t often recall my age or the number of years my wife and I have been married, or, heck, even our kid’s ages. But I recall all the years and dates. In this way, I more easily appear to recall the right value.
- dgellow 6y ago> Don't make your readers hold parts of the sentence in their head. Funny to read this as I'm learning German! In German the main verb of a sentence has to be at the end depending on the context (e.g: if it is a question, or following some prepositions such as "dass"). Let's say we want to build a question, it will be constructed this way: 1. question marker (such as "Was", "Wo", "Warum", etc) 2. subject 3. other details regarding the subject (adjectives and others) 4. the verb, with correct grammatical form depending on the subject Something I find quite frustrating is that I have to keep in mind everything about the subject during the entire duration of the sentence just to be able to use the verb correctly. So because of this I always try to keep the distance between a subject and the verb as short as possible when trying to speak German, which results in very terse sentences that looks similar to what you described. My life partner speaks native German and doesn't even realize that she does this buffering.
- nicbou 6y agoI was just thinking about German the whole time. I knew a German to Polish translator and she complained about how hard live translation was when a key part of the sentence is held until the very end.
- wrycoder 6y agoTen minutes into his lecture, the German professor exclaimed to his restless audience, “Don’t leave yet, I was just getting to the verb.”
- j4yav 6y agoI learned Dutch, which does the same thing with the verb, and at one point after a few years it just clicked and started feeling natural to structure sentences that way. I've been living abroad long enough that occasionally I catch myself trying to organize English sentences in that way as I'm speaking (which, of course, results in falling flat on my face at the end.) In Dutch at least, you can imagine these really long sentences which build up details, adding more and more, until they finally surprise you with the verb at the end. But in practice people don't speak that way - the patterns of speech and just the way people use the language in different subtle ways mostly prevents that from happening, in natural ways that don't feel terse. It may be different in academia/legal professions and that sort of thing.
- pbhjpbhj 6y agoOr just have a proper online form that asks for your DoB and leads you through entry of the necessary info. FWIW in UK 'must' in gov advice indicates a legal obligation. It annoys me no end when such obligations are not supported by references to legislation: as then I can't check if they've been correctly interpreted. Prose should be readable, but also functional.
- nicbou 6y agoThat works for forms. I write static content. I did start adding little calculators and utilities in my articles, but those only make sense because I have a lot of free time. I heavily cite sources, so at least you'd know the exact paragraph in the law that supports it. It's something my competitors neglect, and it makes it hard to tell facts apart from hearsay.
- MaxBarraclough 6y agoThe worst of the three versions you've given is the second, as it makes use of a sentence which, taken on its own, is a lie. It's poor writing to state a mistruth and then whittle away at it until you arrive at the truth. Far better to build up truth upon truth until you arrive at the full picture. Bad: A natural number greater than 1 cannot be expressed as the product of two smaller natural numbers, if it is prime. Good: A prime number is a natural number greater than 1 that is not a product of two smaller natural numbers. (Stolen from Wikipedia.)
- nicbou 6y agoIt still requires a fairly large buffer. It could be improved with some punctuation. A prime number is a natural number that is greater than 1, and not a product of two smaller numbers. Commas let you catch your breath and flush the buffer. When there are two many commas, I use a bullet list.
- MaxBarraclough 6y agoMy point was there's an additional anti-pattern at play. As the reader progresses through a sentence, they shouldn't have to mentally cross out previously made categorical claims. This isn't quite the same thing as the stack overflow problem. I'm afraid I don't see your rephrasing as an improvement. It doesn't substantially restructure the sentence, and to someone familiar with the mathematical writing style, it reads less naturally.
- stared 6y agoI think you gave a good reason why passive voice is preferred in some situations. To me (I am not a native speaker), the default emphasis is on the first words: The police stopped the riot. -> emphasis on the police The riot was stopped by the police. -> emphasis on the riot It coincides with the examples in which passive voice is recommended. > To make something less hostile - 'this bill has not been paid' (passive) is softer than 'you have not paid this bill' (active). > To avoid taking the blame - 'a mistake was made' (passive) rather than 'we made a mistake' (active). ... Yes, I agree that we often overuse passive voice, and active voice is a good default. However, I think that the rule of thumb should be "write in the natural order", rather than "don't use passive voice unless strictly necessary".
- not2b 6y agoThe overwhelming reason why bureaucrats (either those in government or in corporate middle management) love the passive voice is "to avoid taking the blame" (or to avoid appearing to blame someone powerful).
- naniwaduni 6y agoNone of this can really be pinned on the use of passive voice. Attention is naturally drawn by the beginning of a sentence and to the end of it, and while the passive is a powerful tool for reordering sentences, its function is equally well served by verbs with the opposite alignment. There is nothing about "there were mistakes" or "mistakes happened" that attributes more agency to anyone than "mistakes were made", but only the last one is passive. Rather, there is a rich history in English prescriptivism of misdiagnosing and blaming the passive for all ills. http://www.lel.ed.ac.uk/~gpullum/passive_loathing.pdf http://www.lel.ed.ac.uk/~gpullum/passive_loathing.pdf
- microcolonel 6y agoI might go for: If you are 60 years old or younger, fill form 331. If you are older than 60 years, fill form 445.
- karmakaze 6y agoI really don't like style (2). It starts with a false/incomplete statement. Diffusing bomb model AX72 steps: - Cut the blue wire. - But first cut the red wire.
- T-hawk 6y agoI think none of those is the best way to write this. Start with the conditional first, so the reader knows a branch is coming. Then have the most common case immediately following. Invert the conditional if that's necessary to put the common case first. Restating the opposite of the conditional can make it even clearer. "If you are age 59 or under, fill form 331. If you are 60 or over, fill form 445."
- ggggtez 6y agoThe last one is only good if you actually read it. I might end up seeing the first clause, assuming the entire line is irrelevant, and moving on without seeing the "Otherwise". Prefer declarative statements: "If you are 60 or older, you must fill form 445. If you are 59 or younger, you must fill form 331."
- StavrosK 6y agoBut I can't short-circuit those, so I have to read all of them just in case multiple apply.