lostintangent

20 ms·

181.
by lostintangent 9y ago
I love that explaination! I’m a PM on the Live Share team, and like was mentioned, the use case we’re currently focused on is seeking and receiving ad-hoc assistance or feedback from a friend/colleague, in a way that can potentially be
182.
by lostintangent 9y ago
Nice work! This looks really awesome, and is another great example of the passion around better collaboration tools for developers. Thanks for sharing this. With Live Share, we're also looking to extend the collaboration experience bey
183.
by lostintangent 9y ago
Thanks for this feedback! We believe that Live Share's ability for developer's to work together in real-time, while choosing to "follow" each other, or temporarily/periodically investigate something independently (e
184.
by lostintangent 9y ago
Code reviews are definitely a scenario we believe can benefit from Live Share, regardless which version control workflow your team is using (e.g. PRs, trunk-based development). In addition to being able to quickly seek help, we want Live Sh
185.
by lostintangent 9y ago
Remote development is definitely an adjacent use case that we believe could be really compelling. Thanks so much for providing the +1 on the scenario, and stay tuned (i.e. sign up :)) for future updates!
186.
by lostintangent 9y ago
Awesome! Thanks for this feedback. Swarming is definitely a scenario we'd love to see Live Share help improve. And no, collaborators wouldn't need to be running admin level in order to participate in a sharing session. We want to
187.
by lostintangent 9y ago
Absolutely! Live Share allows developers to quickly/easily collaborate with each other, while continuing to use their pre-configured editor, which includes themes, key maps, extensions, etc. This way, everyone can feel completely at ho
188.
by lostintangent 9y ago
It's really exciting to see the energy being directed at improving developer collaboration!
189.
by lostintangent 9y ago
Great question! The project would be built on the machine of the developer who initiated the Live Share session. That developer is effectively the "owner" of the session, and all developers who join the session are connecting thei
190.
by lostintangent 9y ago
That's great to hear! We definitely believe that collaborative debugging is a critical component of being able to demonstrate/reproduce issues, as well as validate changes made during a collaborative/pairing session. We look
191.
by lostintangent 9y ago
We're definitely very serious about Visual Studio Code :)
192.
by lostintangent 9y ago
PM on the Visual Studio Live Share team here. Thanks for posting! We're really excited to hear folks thoughts about this experience, how it can help improve their existing team collaboration workflows, and how we can continue to improv
193.
by lostintangent 11y ago
We (the CodePush team) would love to discuss what that kind of integration might look like :)
194.
by lostintangent 11y ago
Yep we do! We don't support updating assets on Android yet but we will as soon as the necessary platform support is released (should hopefully be in RN 0.19.0)
195.
by lostintangent 11y ago
I may be misinterpreting you, but I'm taking this as a huge compliment :)
196.
by lostintangent 11y ago
As a team of web devs who love mobile, we definitely wanted to help bring as much of this kind of update experience to client apps as possible. I look forward to hearing any feedback you may have after giving us a try :)
197.
by lostintangent 11y ago
We definitely don't want to encourage "abusing" the service by producing poorly tested updates. We're planning to do some work/docs to help incorporating a CodePush deployment into a CI workflow that can choose to r
198.
by lostintangent 11y ago
Yep that's true. I'll add this point to our docs so it doesn't seem like we're trying to manipulate the value of the service. Thanks for the feedback!
199.
by lostintangent 11y ago
We have that button on our backlog! ;)
200.
by lostintangent 11y ago
This compelling opportunity is what made us decide to build CodePush!
201.
by lostintangent 11y ago
Thanks for bringing this up! We definitely need to do a better job raising this point in our docs. That said, I hope this limitation doesn't make it "too good to be true". From the many Cordova/React Native devs we'
202.
by lostintangent 11y ago
We've only just initially added clients for Cordova and React Native, but we plan (and would love to work the community) to build clients for other platforms, so dynamic updates of code and/or content could be easier.
203.
by lostintangent 11y ago
That kind of "power user" experience would totally be possible using CodePush. Thanks for mentioning it, since we should have a sample to illustrate how it would look!
204.
by lostintangent 11y ago
We added CodePush support for React Native because we think it's an extremely compelling platform and so do many of our customers. I actually respect Facebook's pragmatic approach to software development prioritization, and they w
205.
by lostintangent 11y ago
I work on the CodePush team and we are simply interested in helping devs engage more closely with their end-users, by delivering value more quickly and hopefully less obtrusively. We by no means want to prescribe poor and/or annoying u
206.
by lostintangent 17y ago
That's a great point gexla. I wasn't taking into account contractors in the article (naively so). I'll add an annotation to the article that mentions how contract work is slightly different.