3 ms·
I have been a professional developer for 20 years, 10 of those remote. He is right. If people learn how to work and communicate through async text, you can come
by odshoifsdhfs 6y ago
I have been a professional developer for 20 years, 10 of those remote. He is right. If people learn how to work and communicate through async text, you can come up with ideas, exchange thoughts quite easily. Problem is, most people love to hear themselves talk so dismiss ways where they aren't the 'center of attention'. I would say in 20 years, less than 5% of the 'meetings' or 'coffee chats' couldn't have been done through slack/irc/whatever.
- nottorp 6y agoAsync is the keyword here. Have several text channels, some with a specific topic, some more random. Get people used to posting in them and reading them once in a while. Get people used to move to one on ones and/or ad hoc small group chats when they have something to say. Yeah, just like irc. What do you think Slack is modeled on? And just to make myself more hated, cut the scheduled meetings down. If everyone is spamming status in #general (or #status or whatever) you don't really need them. Oh and, like the parent poster, been doing this for at least 15 out of the last 20 years.
- postalrat 6y agoMaybe that works when you have thousands of users like here in hn. I don't see much value in it with a team of 6 people.