One week into VR Coding

by

... and it has lost the excitement. 

The problem is that I've learned just enough to get myself into situations that are harder to troubleshoot. I'm trying to code adjustments to the physics of thrown objects such that they depart from realistic physics in ways that streamline their use as tools within a game. But each type of object having its own physics, with its own reactions to the other objects... it is creating unexpected interactions. Bugs, if you will. 

And I simply don't have the troubleshooting experience in VR to quickly find and correct them. I'm sure an experienced Unity dev would fix these quicly and easily, but I'm not there yet.

Which leads me to believe I've bitten off more than I can chew. I tried to fly too high, too fast. I need to instead stick with simplicity while I learn, and come back to complexity when I know enough to handle it.

And really, that resolves the concern. I was trying to decide whether to keep going on this project or to drop it. But I think the answer is neither - it is to pursue simpler projects for a while, and come back to this vision when the time is right.

I admit, this new journey is going to turn this blog into something new - no longer will I post things a few times a yaer that I hope other people relate to. Instead, this is going to be a personal journal to sort out thoughts as I navigate working on new projects in new areas. 

I would say thanks to the people who read all this, but I do have some basic analytics on this site, and I know that there are no such people. This blog is just me typing at myself. But maybe as I evolve what I do, that too shall change. We shall see.