1. Hard cases make bad law 2. That problem exists in spades with email/irc, which are actually firehoses but pretend to be async
-
-
Replying to @wycats @DPritchett
What I mean by that is that in practice momentum can build rapidly on email threads, and waking up to the end of one of those threads 1/
1 reply 0 retweets 0 likes -
Replying to @wycats @DPritchett
actually feels *worse* because at least on slack "let's wait for Sarah" is a thing that seems reasonable to say. Momentum is subtle. 2/2
1 reply 0 retweets 1 like -
Replying to @wycats @DPritchett
Sending that message, Sarah got pinged and "had to" join the conversation. Slack creates expectations due to its synchronous/instant nature.
1 reply 0 retweets 0 likes -
Replying to @moystard @DPritchett
DND in Slack (et al) means (1) she isn't pinged; (2) people can see that right away. The problem is email pretends you can wait, 1/
1 reply 0 retweets 0 likes -
but that isn't always true. Momentum builds, and email etiquette doesn't have a good (polite) way to halt the conversation for someone 2/
1 reply 0 retweets 0 likes -
to chime in. 3/3
2 replies 0 retweets 0 likes -
Replying to @wycats @DPritchett
pushing people to articulate their thoughts and, in my opinion, often increase the overall quality and output of a conversation. 2/2
1 reply 0 retweets 0 likes -
Replying to @moystard @DPritchett
I think discussions that directly result in decisions should happen using something like the Rust/Ember RFC process, which has the 1/
1 reply 0 retweets 0 likes -
benefits you're describing. I talked about it here: https://github.com/yarnpkg/yarn/issues/274#issuecomment-244784173 … 2/2
1 reply 0 retweets 0 likes
From the Rust RFC introducing the current governance model.pic.twitter.com/fRGbtAQMUh
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.