greptilian logo

IRC log for #openknot, 2016-03-12

Open Knot Communications Platform - https://github.com/openknot

| Channels | #openknot index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
00:02 pdurbin I guess at https://twitter.com/JeffSpies/status/708123813830119425 I'm really being asked about chat for developer communication with respect to flow.
00:03 bear that was my take on his question
00:03 pdurbin I guess what he's calling flow I call being "in the zone".
00:04 bear yes, flow == zone
00:04 pdurbin yeah, I put headphones on when I need people to stop bothering me. close chat. close email.
00:05 bear I keep a couple osx spaces setup with terminal/editor combinations
00:05 bear so when I'm working I don't see the chat/email space
00:05 pdurbin big headphones. so people can see them as they are approaching my desk :)
00:05 bear haha
00:05 pdurbin no little earbuds
00:07 pdurbin bear: that makes sense. as long as notifications don't show up in the space where you're working
00:07 bear yea, I use sound notifications
00:07 bear so when i'm focusing I turn off the external speaker
00:08 bear i'm trying to introduce pagerduty as the method to interrupt
00:08 bear so people get the fact that it's an INTERRUPTION
00:10 pdurbin I'm thinking about the times that I truly need to interrupt a developer.
00:11 bear for us it's only during an incident
00:11 pdurbin I guess if I'm blocked and the developer has been unresponsive to email or whatever.
00:11 bear as they may be needed to help debug
00:11 bear yea, focus time needs to be known blocks
00:11 bear otherwise people will use focus time to avoid being tasked
00:13 pdurbin Huh. I'm not sure that makes sense to me. Focus time should probably be the default.
00:16 pdurbin "Give people long uninterrupted stretches to get work done." https://m.signalvnoise.com/is-group-chat-making-you-sweat-744659addf7d
00:16 bear sure, if they are pure dev in role
00:16 bear I work with a lot of folks who need to support what they build
00:16 pdurbin Ok. Netflix model.
00:16 bear yea
00:17 pdurbin So you only let them focus when something's down? ;)
00:17 bear hahahaha
00:18 bear i'm noodling on a pagerduty rotation that gives everyone 2-3 days of focus
00:20 pdurbin per week?
00:21 bear yea, weekly minimum
00:22 bear just a known chunk of time when they can turn off chat
00:23 pdurbin What about "fear of missing out" from the article? When the turn chat back on are they expected to scroll back and read everything?
00:23 bear yea, that's a hard one
00:24 pdurbin I won't even ask about email then. I assume they're expected to catch up. :)
00:24 bear thankfully our email load is tiny
00:24 bear the email load being small comes from them doing everything in chat :/
00:25 pdurbin Well, email *is* good for annoucements. And when you want to write a few paragraphs.
00:25 pdurbin Of course, a blog post with a link is probably better. :)
00:26 bear yea, email should be used more for those items
00:26 bear you can filter and batch them
00:26 pdurbin I'm all about links. Public email archives with links. Chat logs with links to individual lines.
00:28 pdurbin maybe "announce" lists should be used more. so people can't reply :)
00:34 pdurbin We switched to daily meetings relatively recently. I have mixed feelings about them.
00:35 pdurbin bear: what's the story for meetings for you?
00:35 bear we have a couple manditory meetings - all on tuesday
00:35 bear then it's per team
00:39 pdurbin batching meetings on one day sounds good
00:40 bear +1
00:41 pdurbin bear: how would pagerduty allow a *person* to interrupt someone? I assume it would be a nagios or whatever sending interruptions.
00:42 bear chatbot
00:42 bear /page bear
00:42 bear /page bear "reason or you won't get a response"
00:43 pdurbin ah. ok
00:44 pdurbin bear: and you're more or less happy with group chat? Better than email?
00:45 bear much better than email, but not happy
00:45 bear I want a forum + chat + email hybrid
00:47 bear email = announce; forum = discussion; chat/video = meetings
00:47 bear what happens in chat/video should always get pushed to forum
00:47 pdurbin pushed? how?
00:48 bear meeting notes; fyi pointers to urls of chat logs -- anything really
00:48 bear chat about it but always summarize to the forum
00:48 bear (note -- I haven't ever seen this happen properly; just my dream setup)
00:49 bear in a lot of ways this mirrors the "how do we document things" discussion
00:50 bear because the chat/forum/email issue (and where the dividing lines happen) are also what happens between large teams but normally with documentation
00:51 pdurbin bear: would a recording of the video be pushed to the forum? from the meeting
00:51 bear we are exploring that now with our weekly meetings
00:51 bear to allow timezone folks to not have FOMO
00:52 pdurbin Life may be too short to watch recordings from meetings. Especially the ones I missed while on vacation. :)
00:52 bear :)
00:52 bear meetings that follow agendas are the key for that
00:53 pdurbin how long would the recordings be? 15 minutes? an hour?
00:53 bear our weekly meeting goes 30 to 45 min
00:53 bear IMO 35 minutes is the sweet spot
00:54 pdurbin woof. yeah, life's too short
00:55 pdurbin speaking of which, science fair posters are done. now my daughter and I are going to watch Indiana Jones
00:55 pdurbin bear: thanks!
00:55 bear enjoy!
02:15 * pdurbin replies with a link back here: https://twitter.com/philipdurbin/status/708475802476740609
02:15 pdurbin bear: watched half of it. Gotta get the kids to bed.

| Channels | #openknot index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

Open Knot Communications Platform - https://github.com/openknot