From the last couple of seconds in the video, it appears that Greg is in a wheelchair, and that the object in his right-hand it a mobility-assistance device of somesort. Either way, it is awesome to see that Greg is a successful developer. There is a
web-developer in my city who is pretty well-known. He has a rather successful history of work here, and yet he doesn't write any code with his hands. He has a paralytic-condition which keeps him in a wheel-chair, and he actually writes code with an object
attached to his head. He is amazing.
Ion Todirel wrote:hey Charles, what was in the right hand of Greg?
You're exactly right - it's my splint for typing...
Is your team the same team that developed Visual Source Safe? If so, when was the decision made to drop VSS, and start development on FASTDash? Secondly, why did you decide to go with a completely different application, instead of developing VSS to the level
VSS is a full-fledged source control system - FASTDash is a team-awareness visualization meant to work *on top* of a source control infrastructure, so we're not really trying to replace anything that's already there. Improving and integrating the vis into
an existing SCM solution would probably be a great progression - but we're in Research, not in the product teams, and there's still more research to do...
But what about when you are working on a function and as a reference you just hop to another file to see another functions implementation. I assume it will show up as if you are working on that function while you are only looking at it, I can imagine this could
confuse some your co-workers.
Is it possible to use it over the internet? Lots of activity going on so if it uses allot of bandwidth, and how about security? Because using it in teams with people spread over different locations would be really useful.
We are able to detect when you're editing vs. just not editing, so we can reflect that in the vis.
In our prototype we took advantage of the corporate network for security and used SQL Server. But there's no reason it couldn't be re-designed as a web service for wider geographic dispersion if introducing a little more lag was acceptable.