6 ms·
> There are two camps: the we-should-just-use-irc camp, and the we-need-every-feature camp. I'm firmly in the "email should be used for substantive discussions
by philwelch 8y ago
> There are two camps: the we-should-just-use-irc camp, and the we-need-every-feature camp.
I'm firmly in the "email should be used for substantive discussions" camp, but ever since we got the bandwidth and CPU necessary for the internet to not be a primarily text-based medium, the illiterates took over and that was the end of that.
- smt88 8y agoEmail has a lot of problems, but the dealbreaker for my company is that it isn't secure.
- bigiain 8y agoAnd you somehow trust Slack as a "secure alternative"?
- smt88 8y agoWhere did I imply that? There are tons of options for business chat. My point was only that email isn't even in the running.
- tathougies 8y agoIf you want secure emails use GPG. Unlike slack, GPG is both open-source and offers government-level security. I don't think slack is more secure than GPG.
- spookthesunset 8y agoAnd how does that work for your average person using outlook / google for email?
- tathougies 8y agoThen build on top of email, instead of developing yet another 'secure' proprietary system.
- maw 8y agoIf that were viable people would already be doing it. It's not, and so very few people are. I wish this weren't the case but it is.
- closeparen 8y agoCompanies are generally at more risk from failure to produce message content in a lawsuit, regulatory action, HR investigation, etc. than from eavesdropping. "Secure" in a corporate setting means subject to IT's surveillance, filtering, and archiving. If anything, security's job is to make sure employees aren't using things like PGP, personal webmail, Facebook, etc. to evade corporate retention policies. Maybe mysterious quasi-state actors will steal your secrets and outcompete you decades from now, but they could probably do that anyway. The SEC will certainly fuck you up right now if you can't demonstrate adequate controls on regulated employees' communications.
- tathougies 8y agoI'm talking about personal e-mail. Still businesses can easily enforce retention policies with PGP by using a master key.
- closeparen 8y agoThe security model for internal email on a corporate email server is pretty similar to a corporate slack instance.
- smt88 8y agoI've never seen any email system used securely. Even smart people will send sensitive info to a personal address instead of corporate, for example. Email wasn't purpose-built for controlled internal comms. Part of this is a UI problem, but it's still a problem. I didn't say Slack is the answer, either. Just that email isn't a serious competitor to Slack.
- pm90 8y agoThat's a little too harsh. Not everyone is good at expressing themselves through an email chain; doesn't mean they're illiterate though.
- eric_h 8y agoIt's very much a learned skill. I was fortunate to learn it well in school (and polish it further in my professional life). People who haven't learned to express themselves clearly and concisely are indeed to the left of me in the spectrum of literacy. But again, it can be learned by everyone, it just takes time and effort.
- philwelch 8y agoNot everyone is good at expressing themselves in a real time conversation, either. Any medium of conversation excludes people who aren't good at that medium. But if you have to choose a medium of conversation, are you better off choosing one that excludes introverts, non-native speakers, and people who aren't loud and obnoxious enough to command the room? Or would you rather exclude people who lack the patience or intellectual ability to read or write more than two or three lines of text at a time? Which choice allows deeper and more thoughtfully considered ideas to enter the discussion? I'm loud and obnoxious enough to thrive either way, but I really don't want important professional decisions to be made by the "rofl tl;dr" crowd.
- lovich 8y agoThat's kind of a false dichotomy you've got going there. Introverts and non native speakers are all slow deep thinkers who need a thinkers medium to communicate, which is slow by your definition. Everyone using a quick communication medium is a moron though right? I assume that's what you meant by people who lack intellectual ability. They are just different mediums. Long form is better for getting across new ideas that have to be explained for the first time, but a medium like emoji allows for incredibly dense communication with single glyphs once the meaning has been established
- philwelch 8y ago
- tomnipotent 8y agoEmail is crap for many types of workflows that Slack excels in.
- toomuchtodo 8y agoIt’s too bad most of those workflows don’t apply to business use cases. Is it a chat client? A knowledge base? A conference call? A command line? Who knows!
- tomnipotent 8y ago> It’s too bad most of those workflows don’t apply to business use cases. Which is totally why Slack isn't popular with businesses. /s Just because you personally haven't found it useful, doesn't mean hundreds of thousands of other business users haven't.
- emodendroket 8y agoBusinesses pay for a lot of stuff that doesn't work. Simply saying everyone else is doing it is not necessarily convincing.
- deleted 8y ago[deleted]
- prlambert 8y agoI'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!!
- Nursie 8y agoThere's way too much noise in my email inbox, stuff gets lost. Important/immediate discussions take place in person, or on slack. (Or hipchat or sametime or lync or windows messenger or hoary old ICQ for all I care...)
- bigiain 8y ago> There's way too much noise in my email inbox, stuff gets lost. I find that happens an order of magnitude more often in Slack than email. The number of times important things here don't get done on time (or at all) because "Oh, I must have missed that in Slack...)
- hfourm 8y agoEmail can also create bottlenecks and unneeded silos of information...
- sequoia 8y agoSorry to get triggered but oh my god I dislike those buzzwords. I find those two come up any time attempts are made to delineate responsibilities or make it possible for teams to run in parallel (by saying "you work on this area of speciality, I'll work on that" i.e. "silos").
- hfourm 8y agoEhhh, you kinda mixing problems here.
- gregmac 8y agoI'm firmly in the "email has no place in internal discussions whatsoever" camp. Tasks belong in tickets, long-term documentation/policies/meeting notes/etc belong in shared space (wiki), and discussions are faster and more productive in realtime (in-person, video call, or chat). E-mail might kick some of this off, or be used to schedule, but that should be it. The problem I think most people run into with the realtime discussion is failing to document the outcome of the meeting -- and that of course goes into a ticket or long-term docs. A meeting with no notes or outcome might as well have not happened.
- alanfranzoni 8y agoYour suggestions may work inside a company. E-mail is the only federated system we've left. If you need to contact somebody outside it, you're screwed. XMPP/Jabber could have solved some of this, but it's pretty dead right now.
- throwaway1555 8y agoThe org I work for has a bunch of Slack channels that we invite our clients into as single channel guests (If they don't already use Slack). We have Gov & corporate using it without issue and they love it.
- keithnz 8y agoI generally agree with greg, and that covers 90% of the cases, for the times where Email is used with external entities, it usually gets dumped into issue tracking / wiki Most work communication is usually within our issue tracking system We use slack very lightly, - most of our conversations are face to face but anumber of remote employees, and slack is used instead of face to face. Often for video calls - copy pasting things to other people - a sort of mini internal HN where links are posted to interesting things in the dev world and we discuss - prodding people "Oi, my PR is still waiting .... " "did you setup ... ?" etc - telling people where we went to lunch so they can find us.
- rrdharan 8y agoI think if you ask Slack about that they'll happily tell you about Slack Grid. EDIT: Whoops actually Shared Channels is the feature I was thinking of: https://slackhq.com/introducing-shared-channels-where-you-can-work-with-anyone-in-slack https://slackhq.com/introducing-shared-channels-where-you-ca...
- ebiester 8y agoEmail: Two use cases. With email, how can I subscribe to conversations I'm interested in? Mailing lists are nice, but we have no real way to make mailing lists that start and stop on the fly like a chat channel in a way that is searchable to the entire organization during or after the fact. What email list system allows for quick creation and the ability for everyone in an organization to know that a conversation is happening and how to join with the ability to get all the context necessary in a chronological order? (Reading threads can get really repetitive in a mailing list, especially when trying to get up to speed on an issue.) You get to all the requirements, and you end up with a discussion board instead or a new product that is to email lists what slack is to chat. Email is great for some things, but there's a reason people use slack instead even when they already have email.
- sokoloff 8y ago> Mailing lists are nice, but we have no real way to make mailing lists that start and stop on the fly like a chat channel in a way that is searchable to the entire organization during or after the fact. Isn’t that what subject lines and mail archives are useful for?
- ebiester 8y agoWhat's the mail archive that can be set up with the same ease of use and permissions as slack? What, are you going to say hypermail? Nobody has put together a simple solution in the mail domain. Maybe there's a market for it - turns out someone might pay for it if it's better than the slack experience.
- philwelch 8y ago> You get to all the requirements, and you end up with a discussion board instead or a new product that is to email lists what slack is to chat. This would also be acceptable IMO. Any medium that enables asynchronous long-form written communication has advantages that are fundamentally impossible for any synchronous chat medium to match. It turns out that listservs have successfully done this for decades. If there was even a fraction of the effort invested in this communication style as is invested in reinventing IRC with emoji and reaction gifs, I'm sure it would be even better.
- spookthesunset 8y ago> the illiterates took over and that was the end of that. That's pretty arrogant. Perhaps people have different communication styles than you. Not better, not worse... just different.
- philwelch 8y agoWhat word would you use for people who are incapable of communicating through the written word? Or for an Internet that is increasingly designed to cater to such people? The dialup-era Internet was mostly text and a little bit of pictures. There was good text, bad text, and lots and lots of fanfiction, but at least it was text. Even if you went to The Onion, there might be one goofy photoshopped photo but you had to read an actual article with real paragraphs to get the jokes. Now everything is a video, or a picture, or a meme, and everything longer than 140 characters is “tl;dr”. That’s a cultural decline akin to when television displaced reading in the mid-20th century. I can communicate in either style, so it’s not a personal thing from my perspective—except, since I can communicate in either style, I can also tell which style is more conducive to deep and meaningful discussion.
- u801e 8y ago> I'm firmly in the "email should be used for substantive discussions" camp I wish there were more people who were in the "newsgroups should be used for substantive discussions" camp. They're better than email in that context.
- philwelch 8y agoI never had a chance to get into newsgroups that much, but I believe you.
- KyeRussell 8y ago> the illiterates took over and that was the end of that. That's a very harsh attack and I'm sure you're aware of all the nuances you're conveniently skipping over. I'm not sure how you think this adds to the discussion at all.
- paulie_a 8y agoEmail has unfortunately become "I don't check it or care anymore" I am flooded with automated notifications that basically are "who gives a shit". I think the main reason I use email is for password reset. When you receive 1-2 thousand emails of non-spam but still unimportant cruft, it gets ignored or overlooked. Email is pretty much dead to me as a meaningful way to communicate. Sidenote: the term "ping me" needs to go away.