<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>communication · Daniel Sada</title><link>https://danielsada.tech/categories/communication/</link><description>Daniel Sada writes about developer productivity, engineering culture, AI and the software that saves him 100+ hours. Mostly in English, sometimes en español.</description><generator>Hugo</generator><language>en-US</language><managingEditor>hello@danielsada.tech (Daniel Sada)</managingEditor><lastBuildDate>Sun, 22 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://danielsada.tech/categories/communication/index.xml" rel="self" type="application/rss+xml"/><item><title>Assume People Are Not Interested in Your Blog Post</title><link>https://danielsada.tech/blog/assume-people-are-not-interested-in-your-blog-post/</link><pubDate>Sun, 22 Nov 2026 00:00:00 +0000</pubDate><guid>https://danielsada.tech/blog/assume-people-are-not-interested-in-your-blog-post/</guid><description>&lt;p&gt;If you do not write for other people, stop reading this now.&lt;/p&gt;&#10;&lt;p&gt;When I was at Snowflake, one of the coolest things that everybody did was this etiquette thing. The first sentence of each email would be &amp;ldquo;If you don&amp;rsquo;t develop in this specific part of the code, you can stop reading.&amp;rdquo; or &amp;ldquo;If you&amp;rsquo;re not part of the finance org, you can stop reading.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;This made me think a lot about what it means to write for other people. You need to be subservient to your audience. Similarly, thinking about how much space you take is very important. For Slack/Teams threads, you would start with a 3- to 5-line introduction to your topic, and then people could find more details inside the threads.&lt;/p&gt;</description></item></channel></rss>