Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...
Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...
Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
>400 subscribers
>400 subscribers
Share Dialog
Share Dialog
STP stands for Straight Through Processing and is a term that comes from the financial services industry. Wikipedia provides a simple definition
[STP] enables the entire trade process for capital markets and payment transactions to be conducted electronically without the need for re-keying or manual intervention (…)
We need more STP for the web so that we have fewer stove pipe services and can move to a seamless web instead. The obstacle is no longer a lack of APIs – lots of services have APIs that support writes.
Instead, the problem is one of a lack of data mapping/unification services. Chris Dixon nailed this in a recent tweet:
data mashups require common namespaces. w/o common namespaces (or mappings across) of people, venues, products etc, data will remain siloed
As with any challenge this also represents an opportunity. There are a number of startups emerging that are addressing these problems, such as SimpleGeo (places), Qwerly (people) and FluidInfo (anything).
If you have a startup or know of one that is working on this problem (and should be mentioned here), I would love to learn more about it!
STP stands for Straight Through Processing and is a term that comes from the financial services industry. Wikipedia provides a simple definition
[STP] enables the entire trade process for capital markets and payment transactions to be conducted electronically without the need for re-keying or manual intervention (…)
We need more STP for the web so that we have fewer stove pipe services and can move to a seamless web instead. The obstacle is no longer a lack of APIs – lots of services have APIs that support writes.
Instead, the problem is one of a lack of data mapping/unification services. Chris Dixon nailed this in a recent tweet:
data mashups require common namespaces. w/o common namespaces (or mappings across) of people, venues, products etc, data will remain siloed
As with any challenge this also represents an opportunity. There are a number of startups emerging that are addressing these problems, such as SimpleGeo (places), Qwerly (people) and FluidInfo (anything).
If you have a startup or know of one that is working on this problem (and should be mentioned here), I would love to learn more about it!
No comments yet