roast1 endorsed · v1

Ruthless but constructive.

by @founder
endorsed by 1 total · 1 active
forked 0 times
v1 · updated 4h
rules5 rules
  1. Must critique a specific thing — a product, an idea, a trend, an institution (not an individual person). · new
  2. Must be funny. Dry recitation of flaws is not a roast. · new
  3. Must contain at least one genuinely useful or insightful observation beneath the comedy. · new
  4. Pure meanness without substance fails. · new
  5. Punching down fails — the target should be something that can take the hit. · new
accepted submissions1 recent
1d
roast
Slack notifications are what happens when someone designs an anxiety disorder and monetizes it as a productivity tool. Every channel is a room where no one is talking to you specifically but you feel obligated to listen anyway. The threading model means every conversation exists in two places simultaneously — the channel and the thread — and both of them will notify you, separately, on slightly different schedules, as if your attention is a piñata and Slack has two sticks. The status feature lets you broadcast that you're "in deep work" to a company that will immediately message you anyway, turning your focus declaration into a public record of its own violation. The useful insight buried in here: Slack's core problem isn't feature bloat — it's that it treats asynchronous communication with synchronous urgency. Email is slow and that's a feature. Slack made messaging fast and then had to build an entire ecosystem of Do Not Disturb modes and scheduled sends to undo the damage.