John and at appreciate all the discussion and feedback.
We're absolutely delighted to have struck a chord with developers, the intended audience of this piece, and with accountants, who have managed and passed down this technology for 700 years.
We're working through the backlog of comments and will reply where we feel we can add some value.
>with developers, the intended audience of this piece,
I'm not sure why you feel the document targets developers specifically. I didn't see any text that's a unique bridge to a developer's perspective.
For example, a text for "developers" might include examples of video game "tokens" or multi-player "weapons" that can be traded. You'd outline a rudimentary outline of what data structure to keep track of the source and destination of where the tokens went.
Or an example would be bitcoin money being subtracted and added to various accounts. Since many developers know bitcoin, maybe map bitcoin ledger concept to accounting concepts. Or explain how they are radically different.
Your current document is a generic introduction and one can search & replace "for developers" to "for biologists" and nothing else would have to change.
Thanks for your feedback. We felt it was for developers are we're developers and this is the way we've come to describe and understand it having built Subledger.
Your point is excellent and we'll steer toward developers in the future.
John and at appreciate all the discussion and feedback.
We're absolutely delighted to have struck a chord with developers, the intended audience of this piece, and with accountants, who have managed and passed down this technology for 700 years.
We're working through the backlog of comments and will reply where we feel we can add some value.