8 ms·
I'm curious as to how that breaks down? Which kind of workflows are best in email, which in Slack?
by prlambert 8y ago
I'm curious as to how that breaks down? Which kind of workflows are best in email, which in Slack?
- sequoia 8y ago_This_ is the 64 thousand dollar question that no one seems to have a clear answer to, and leaves people frustrated with both email and slack. I tried emailing longer form things at my current job and rapidly hit a cultural wall: people _do not like_ getting long emails, or emails with more than 1 or 2 replies. Slack people apparently have no problem with because it's "lighter weight", but I struggle to see how always-on disruption is lighter weight than check-it-a-couple-times-per-day email. I think a deeper problem is lack of delineation of responsibility and adequate planning. Slack & other "always on" communication systems make it easy to say "why plan? I can _just ask_ when I need to know something" or "we'll have a conversation" rather than specifying & recording or relying on a more rigid interface like a ticketing system. tl;dr: get off my lawn you dang kids!!
- dasil003 8y agoFeatured specifications work better in email, live debugging/forensics work better in Slack.
- kasey_junk 8y agoFeatured specifications work better in source control...
- u801e 8y agoYou can have both with git format-patch/git send-email and git am :)