This is quite comparable to the vision I had in 2012 for NuzzGraph, but there was no way I was going to realistically make any real progress given the complexity and my lack of experience at the time.<p>Also it was clearly a solution in search of a problem. I was a believer in the idea that graph databases would enable a new paradigm of application development in the way that relational databases did, and wanted to try to pioneer something. That was (so I thought) what college dropouts like myself in my early 20s needed to do to get ahead in tech, as I was only a mere data analyst at the time, with no connections to the tech industry, scraping by while living inside a garage.<p>It was a good exercise though and it somehow out of sheer luck caught the attention of Manning Publications as it likely came up in the search results for OrientDB. My project page included a sort of roadmap to integrate with OrientDB.<p>They signed me on as a co-author of the book OrientDB in Action as the other author(s) IIRC weren’t native English speakers and they needed one. The book was never released but a different author released a similar book without publisher backing which was good enough for OrientDB.<p>If a publisher ever approaches you to help write a book, no matter how ridiculous of a candidate you think you are, your initial response should always be yes. You don’t have any obligation to actually finish a book unless it’s in the contract. You won’t make a dime but you’ll get world-class training on writing technical documentation. They only required that I complete a draft of one chapter within a shorter timespan for the first phase.<p><a href="https://code.google.com/archive/p/nuzzgraph/wikis" rel="nofollow">https://code.google.com/archive/p/nuzzgraph/wikis</a><p><a href="https://code.google.com/archive/p/nuzzgraph/wikis/NuzzGraphBenefits.wiki" rel="nofollow">https://code.google.com/archive/p/nuzzgraph/wikis/NuzzGraphB...</a>