Have you had success with remote synchronous pair programming over VC? If so, what tools does your team use to be effective?
-
-
En réponse à @ericwryan
ScreenHero was great for this before Slack ruined it. There's a new effort (Tuple) to make Screenhero again https://screenheroreplacement.com/
1 réponse 0 Retweet 1 j'aime -
-
En réponse à @ericwryan
They bought it, shut down the original Screenhero, then changed the code to optimize for voice clarity rather than screen-sharing clarity. As a result sharing your screen now requires extremely high bandwidth and is still fairly spotty. Also weird keyboard/mouse share bugs.
2 réponses 0 Retweet 1 j'aime -
En réponse à @rodhilton
Interesting.
@slack folks.. and plans to invest in the "remote pair programming" use case for Screenhero? Or are you moving in another direction with the product? / cc@rands@beardigsit@roach1 réponse 0 Retweet 1 j'aime -
En réponse à @ericwryan @slack et
That’s some A+ snitch tagging there ;)
1 réponse 0 Retweet 3 j'aime -
En réponse à @rodhilton @slack et
sad that we're a week too late to ask for feedback from
@aunder :)1 réponse 0 Retweet 0 j'aime -
En réponse à @ericwryan @rodhilton et
It's already there! https://get.slack.help/hc/en-us/articles/115003501303-Share-your-screen-with-Slack-Calls …pic.twitter.com/gf4ia4N2Ff
1 réponse 0 Retweet 1 j'aime -
En réponse à @roach @rodhilton et
feedback from some of my team has been that screen sharing latency has degraded recently following the Slack integration. This regression makes pair programming difficult. Is this a known regression you all plan to address?
1 réponse 0 Retweet 1 j'aime -
En réponse à @ericwryan @roach et
+1 I was pairing yesterday with someone and while I was clicking and working in my browser, they saw my ide instead. Image is grainy frequently.
1 réponse 0 Retweet 1 j'aime
Forwarding to the team 
-
-
-
En réponse à @ericwryan @roach
Interested to hear if you have any updates from the team on this?
0 réponse 0 Retweet 0 j'aime
Fin de la conversation
Nouvelle conversation -
Le chargement semble prendre du temps.
Twitter est peut-être en surcapacité ou rencontre momentanément un incident. Réessayez ou rendez-vous sur la page Twitter Status pour plus d'informations.

