3 ms·
Depending on your role, communication on Slack could be as much as 50% of your job responsibilities. Not everyone is a line dev who codes 7 hours after a 10 mi
by antisthenes 3y ago
Depending on your role, communication on Slack could be as much as 50% of your job responsibilities.
Not everyone is a line dev who codes 7 hours after a 10 minute standup.
- cqqxo4zV46cp 3y ago[flagged]
- TeMPOraL 3y agoCorrect. Managers gotta manage, but code doesn't write itself either, and the constant push to turn software engineers into part-time faux-managers (all the responsibilities, none of control or status) isn't helping.
- groestl 3y ago> Not everyone is a line dev who codes 7 hours after a 10 minute standup. Funny enough, those often answer fastest. The busiest communicaters sometime don't answer for days.
- dwaite 3y agoBecause of how malicious notifications are by default in Slack (e.g. @here, @channel, bots you can't mute) and how poorly the catch-up flow is (e.g. no "unreads" view on mobile, I'm in 16 different slacks which have to be tabbed into individually), I tend to catch up 1, maybe 2 times a day. Similar to how when corporate email got pushed into a web view rather than being accessible via a native mail app; the only way I could manage things was to filter into topics, and some topics I only check once a week.
- ruszki 3y agoWhat the previous commenter mentioned is kinda independent on the communication channel if it’s written.
- deleted 3y ago[deleted]