sent2null space

The main gripes I've heard and neutralized are: 1) "Oh but it's so dangerous!! what of drones falling out the sky! what of accidents??" 2) "Oh the government will never allow it, too many laws..too many regulations." 3) Doubts about scale but these are coming from a fear place not a technical place, as an Engineer I can tell you *now* they are moot. 4) Doubts like my brothers which was that people would fear their adoption, that one was easy. We've got a 150 years of new technology being feared and yet still being adopted eventually once all the paranoia was neutralized. We can start with the hilarious madness of the current wars during the late 1870's, we can move up to the late 19th century in the 1890's to see the same hilarious paranoia said about the automobile....fast forward yet again just 10 to 15 years and see the same hysteria go up about airplanes.  The same data devoid and fear based arguments were put up then....all absol

Prologue A few months ago I was thinking about one day writing a book that would describe the best practices that those who implement Action Oriented Workflow or use a framework that implements it could refer to. It would provide an extensive history of how I discovered the action landscape and in my implementation of Action Oriented Workflow sought to model it using an efficient distributed computing framework. A thread on Facebook in which I mentioned casually one day needing to "write a book" on the subject led me to play a bit in photoshop and produce the image shown above. This is a virtual textbook cover of what I'd imagine the book to look like...complete with fake reference to a real publishing company (an inside joke given I once worked there) but the book cover itself may reference something that will never need to be in terms of a formal set of best practices for workflow modeling, as explained below. On the path to the action landscape... Though I