←back to thread

How to Write Compelling Release Announcements

(refactoringenglish.com)
69 points mtlynch | 1 comments | 25 Jun 25 14:22 UTC | HN request time: 0s | source
Show context
deanebarker ◴[25 Jun 25 14:55 UTC] No.44378079[source]▶
Actually, I don't love this. To me, the examples in red are much more helpful -- they explain, in bare terms, what was actually done. The examples in green feel like a marketing exercise to me. Like they're trying to wrap or obscure clear writing in something to obfuscate it.

"Added 'duplicate' button to the event menu" is kind of exactly what I want to read.

I don't know -- maybe have both kinds? A simple, bare-bones set, and then an... "embellished" set?

replies(4): >>44378248 #>>44378305 #>>44378659 #>>44378942 #
pimlottc ◴[25 Jun 25 16:13 UTC] No.44378942[source]▶
I think there's a middle ground here that would be best. The "bad" example tells you exactly what changed, but not why you might care. The "good" example attempts to give lots of context but takes a while to tell you what actually changed.

Just a small title change would help a lot: "Create events 10x faster with new Duplicate button"

replies(2): >>44379044 #>>44379335 #
1. rao-v ◴[25 Jun 25 16:46 UTC] No.44379335[source]▶
Just to add a nit to this, “10x faster” is noise and fluff. Save it for when you actually have a real measured metric that someone might care about. Notice also 10x faster generic event creation is not what the value is! Rather say “Make multiple similar events faster with the new Duplicate button”