author's software principles

Make software that discusses its methods with the user.

Example:
At the heart of basically every application are functions that draw dots, lines, and other geometries. Are these ever discussed in software documentation? To me, this looks like a market niche.

At present, with little to go on but this idea (very limited knowledge of languages, etc.), what I can do is write about it. Since the idea is to inform, anyway, that might do double duty, informing while developing.

That's one principle with an application of it illustrated. Here's another:

Treat virtual reality not as a computing application but as the essence of what computing is and how it's done.

I want to work on the first principle before I tackle the second. The first principle is an approach to the building blocks of virtual reality. The statement of the second principle can stand, here, as an expression of the next larger goal.