8/23/2026 at 10:38:59 PM
My favorite quote from Mark Twain is “I didn’t have time to write a short letter, so I wrote a long one instead”. Indeed, brevity and clarity actually take time and analysis. I find this to be very true when writing requirements or documentation. Some of the worst requirements I’ve read have been extremely wordy and unnecessarily over-technical or jargon-heavy when it could have been explained in plain language. As usual, it very much depends on the target audience.by temporallobe
8/23/2026 at 10:46:47 PM
Incidentally, that's my favourite quote from Blaise Pascal: https://quoteinvestigator.com/2012/04/28/shorter-letter/by necovek
8/24/2026 at 12:35:15 AM
My favorite quote for 10 years was from my 1993 college math professor:You will never go wrong attributing a pithy quote to Benjamin Franklin or Mark Twain.
And then the internet became popular.
by asdfasvea
8/24/2026 at 9:23:43 AM
I think your professor took that one from Franklin... or was it Mark Twain?by necovek
8/24/2026 at 7:18:57 PM
Franklin couldn't predict the future. It was Twain, saying you'd never go wrong attributing a quote to Franklin.by madcaptenor
8/25/2026 at 6:26:32 AM
Respecting a timeline only matters in some universes, and in the Universe of Quotes, it certainly does not!by necovek
8/24/2026 at 2:27:48 PM
When I was in college I read:At a party, want to have people think you're really smart?
If someone asks "Where's that [quote] from?" quickly respond "The Bible or Shakespeare."
In English, you'll be right 50% of the time.
by bookofjoe
8/24/2026 at 7:05:28 AM
If only the LLM coding zealots were aware of this wisdom.by waynesonfire
8/24/2026 at 2:03:06 PM
Yes, but it can be worth it as I've generally found that the most effective professional writing has your high-level request appear within the very first sentence.This is because it as quickly as possible puts the reader into the context of what you need from them making your rationalization of the request reinforce it, whereas if you try to rationalize before getting to your request a busy reader (think customer support, exec, manager) will be thinking "Okay, okay, okay, what are they getting to? Okay, okay, oh there we go finally I know, now let's consider their rationalization, maybe I should scroll up and re-read".
I started doing this after having done email customer service many years ago, when you're expected to spend as little time as possible per support case, you will speed read their writing until you find the part which says what their issue is, for some emails this was paragraphs. A particularly memorable WoW case for me was something like this, but more verbose:
"I finished the raid last night where we managed to down <boss name>, after we celebrated, I logged off. Then I woke up and went to school as usual, after getting home I tried logging on it showed a message saying I was banned, I was heart-broken as I've put so much time into the game and it means so much to me, so to find out why I logged into my Gmail and an email from you said I was banned due to <reason>."
As a support person, all of that was completely irrelevant except for the part saying "I was banned due to <reason>" (which was commonly due account being compromised by a gold seller looting it and then auto-banned due to stuff they were doing on it).
Something else which reinforced my view of "get to the point quickly" was an HN comment saying how they were once sent on a course on "how as an engineer to communicate effectively with execs" which apparently essentially stated "write your email as you normally would, then at the end take the last paragraph and put it at the top of the email". The rationale being that execs are typically only interested in reading a full email if it's actually relevant to them.
by jonathanlydall
8/24/2026 at 2:59:24 PM
This sounds a lot like the BLUF technique [0]. This is one of my favorite techniques in professional settings.I don't interpret this as contradictory to the OP's point and quote: in order to determine the most important first line, one must slow down to identify exactly what that is.
by jodacola
8/24/2026 at 11:36:52 PM
It works in all cases except the important ones, where you expect that your request will be denied upfront and you have to present all the compelling arguments for your request along with the risks of not honoring your request, before you go to formulating what you need as the lesser evil of all the unpleasant alternatives.by sixsevenrot
8/24/2026 at 9:07:12 AM
I find that this quote is not just applicable to writing of natural language like letters. It also applies to code, and is becoming more and more evident to me due to the use of AI.I believe the idea presented transcends writing actually. For example you could also apply it to painting or sculpting. I think this points to the character of creative thinking where one "chips" away at a subject until it is considered as finished.
by trashb
8/24/2026 at 12:50:52 PM
The classic example of writing tight and efficient code is:by WillAdams
8/24/2026 at 8:52:14 AM
Similarly I often read ticket or PR descriptions written by Claude that are so jargon-heavy that I just can't understand on first try. On one side it's a reality check because I always considered English to be close to a mother tongue for me, on the other side I never had to deal with words like "idempotent"... (Seriously, when did this become one of the go-to words to use?)by cpt_sobel
8/24/2026 at 11:18:29 AM
Idempotency is a crucial trait in the world of web APIs (and any other system where commands that modify state might need to be retried due to communication failures). It's not a new word or concept, but it's certainly a niche one.by interf4ce
8/24/2026 at 11:02:58 AM
Idempotent is definitely a word that’s strangely awkward and alien to actually use, but makes reasonable sense when the etymology is known.The closest alternative I can think of is debouncing/debounced
by Modified3019
8/24/2026 at 12:27:57 PM
> jargon-heavyYes. It’s even worse than jargon tho I think it just invents its own metaphors. At first I thought this was clever and useful, helping me to internalize the code (“the normal path vs the escape hatch”) but I’m increasingly finding the metaphors to be so thick and esoteric that it’s actually a hurdle to understanding the actual code.
by joshuahedlund
8/24/2026 at 5:46:52 PM
This brought to mind the often quoted assumption that intelligence and compression are intimately related.A well edited letter may therefore be a sign of intelligence.
by stillpointlab
8/24/2026 at 2:25:00 PM
Classic Spanish proverb: "Vísteme despacio, que tengo prisa." Literally meaning "Dress me slowly, because I'm in a hurry."by bookofjoe