3 ms·
Wow, that sounds awful. Mostly asynchronous Slack/Teams/whatever is so so productive. You need a team that is all committed to deprioritizing message checking a
by IggleSniggle 5y ago
Wow, that sounds awful. Mostly asynchronous Slack/Teams/whatever is so so productive. You need a team that is all committed to deprioritizing message checking and knowing how to @at the right person or group when something is actually urgent in order for it to work though.
- legerdemain 5y agoThat's a privilege that our architect/principal engineer enjoyed. Everyone knew that he was too important to bother, so people generally didn't ask him questions. He'd reach out to you if he needed something, and otherwise he'd scan Slack and code reviews once a day and that was all the comms you'd get from him. He basically delivered solutions, and then it was our job to fix, maintain, and support them.
- ahoka 5y agoWow, that sounds very bad.
- n4r9 5y agoDoes it? They've carved out the essential space needed for deep thinking and are still responsive to questions on a daily basis. Sounds fine to me.
- NotSammyHagar 5y agoIt could be very dysfunctional if someone is throwing stuff over the wall, but isn't so involved in day to day understands of what is needed, what are the problems. That's a hard thing to be successful at, that remoteness.