Prepare your "no" and keep it handy
The article discusses the importance of preparing a polite and effective way to say 'no' to unwanted requests. It suggests writing a concise and considerate refusal in advance to avoid discomfort in high-pressure situations. The author shares their experience of using this method successfully and encourages others to create their own version.
- ▪The author emphasizes the need to prepare a polite 'no' in advance.
- ▪A well-crafted refusal can save time and emotional distress.
- ▪Memorizing the gist of the refusal helps in face-to-face situations.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Derek Sivers |
| Canonical URL | https://sive.rs/n0 |
| Publication time | Sun, 17 May 2026 01:26:20 +0000 |
| Retrieval time | 2026-05-17T01:40:19.096Z |
| Last seen | 2026-05-17T01:40:19.096Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 3J-zsC3Fqtmq |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Prepare your “no” and keep it handy 2026-05-14 Someone asks you to do something, and you feel that pressure to answer immediately. You don’t really want to do it, but don’t know how to say so on the spot. You avoid confrontation, and say OK. You regret it, and later think of how your ideal eloquent self should have said no. I felt the pain of this, over and over again. Then I finally figured out a solution that’s worked wonderfully for years. I took an hour to write a really nice “no” in advance. Considerate, but decisive. Not too long, but not too short. Generalized and versatile for all situations. I saved it on my computer and phone, to copy and paste. Now as soon as I get an unwelcome request? Tap-tap-tap. COPY-PASTE-SEND in three seconds, and it’s out of mind. No anguish.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Derek Sivers.
Discussion
0 commentsMore from Derek Sivers
