During these days in Visual Studio Live @ Austin I have been lucky enough to go to a lot of very good sessions. In example, I’ve seen how Brian Randell or Richard Hundhausen made great DevOps demos concepts using Visual Studio Team Services. I liked a lot how now, when we use Team Foundation in the Cloud, it allows us to explain DevOps concepts almost instantaneously.
This makes me remember my ALM sessions 10 years ago. In those days, we made the first demos of TFS 2005 or 2008 and had to deal with resources for everything. On the one hand I needed a powerful laptop, because usually the demo was running in a virtual machine. There were even more complex scenarios where in addition to the TFS VM, I needed another virtual machine for a Domain Server, another VM for SharePoint, and maybe a couple more.
In those days, I remember that as we needed power, we used to have very big laptops. In my case, I used to travel with one or more external disks where I got “my demo VMs”. And, of course, well the experience of assembly and preparation before an event was not easy at all. I will not deny it, they were moments of many nerves, and also of instant gratification when at the end of the session you received a question related to the topic of the event.
These days I have to deal with something similar, Hololens sessions. Everything seems easy when we watch Build or another big event mixed reality sessions. However, in technical sessions we usually may deal with
- The need for a very powerful laptop. Mostly to be able to use Visual Studio and Unity3D in a comfortable way. This is going back to traveling with big laptops which are usually bigger than an airplane suitcase
- The complicated development flow for this type of projects. At minimum we need one instance of Unity3D, and 2 Visual Studio instances
- The compilation dead times we have for and App or the long deploy times to deploy an App to a device
- The delay we have when the FOV of Hololens is presented. Delay between what the user of Hololens actually sees and what is projected from an external computer.
- The low sense of immersion of the audience when viewing a 2D projection on a projector or similar. When the real experience is lived by the person who is using the HoloLens
While there are some workaround for some topics, such as to improve projection delay, the ideal is to think of the session in a different way. In one year with more than 20 Hololens sessions for groups of users and clients, I have learned to review these points when I prepare a session:
- Based on the time of the session, create a suitable script for the time and content to show. For example, if the session is a session for programmers, it is best to plan a demo moment with a live debugging of an App from Hololens to Visual Studio
- If the session allows you, perform “Live Code”. In this type of example, where a simple Hello world can take a long time to create from scratch, it is best to have 90% of the project/code complete and only add the missing parts live.
- Avoid App deployment times to device. A built and deployed App saves a few valuable minutes in the session
And finally not forgetting the basics
- Review and know in advance the place where the session will be held. It is important to note that Hololens demos need space for the holograms, an adequate light level and also a good Internet connection
I will take all of this in mind for the future Hololens Tour in the month of June, where I’ll be lucky enough to talk about Hololens in the .Net User Groups in Mississauga, Toronto and London. In addition, I am preparing some special surprises for these events, which I will communicate as soon as I can confirm them.
The last days of June will be fun!
Greetings @ Austin