Granted, VR may not be a good input method for bursts of high-speed, high-dexterity input (so, coding), but I can see its advantages in Ops contexts and for rea

Granted, VR may not be a good input method for bursts of high-speed, high-dexterity input (so, coding), but I can see its advantages in Ops contexts and for read-only navigation. Imagine a build pipeline represented as a 3D chain of shapes (one shape per pipeline run). Drag the latest shape in the chain forward, then release it - when it snaps back, you've initiated a new build, with a "ghost" shape left it place to represent that a run is in progress (it will become solid when the run finishes). Pick it up and throw it in the trash to delete a faulty build. Pick it up and place it on a pedestal labelled "release" to deploy it to production. VR will finally leverage Object Oriented Programming in the way it should have been used all along - spatial manipulation of digital objects that use pretty good physical metaphors for what they are.