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
Yesterday we had our portfolio company summit with the CEOs of most of our active investments in our office. It is always a really fun day because there are great discussions about a far ranging set of topics from hiring to business models. This year as an opener we went around the room and everyone talked briefly about a lesson learned in the last 12 months. There were a ton of really good insights there and some really funny ones, such as “it is better to have a hole than an asshole” (about having the courage to fire a key contributor with an attitude problem).
But if one paid close attention there was also a fascinating pattern. One CEO would say something like “we learned that AB testing really works.” And then a couple of people later, another CEO would say “we learned that building what we ourselves wanted in the product gave us the best results.” Or more starkly put, one CEO learned to do more AB testing and the other to do less. Can both be right?
The answer is yes and it is exactly why startups are hard! You can do too much AB testing and you can do too little AB testing. I have to come to think of this as Scylla and Charybdis problems. And there are a great many of them. You can be too early to a market or too late. You can raise too much money or not enough. You can hire too fast or too slow. You can spend too much time on corporate culture or not enough. And so on. Navigating between the two is hard and also means that someone else’s lesson may not apply to you!
The challenge to find the right course will become a new mini series here on Continuations. I will pick one of these and explain how you can go wrong on either side. Please let me know your own favorite examples to be included in this.

Yesterday we had our portfolio company summit with the CEOs of most of our active investments in our office. It is always a really fun day because there are great discussions about a far ranging set of topics from hiring to business models. This year as an opener we went around the room and everyone talked briefly about a lesson learned in the last 12 months. There were a ton of really good insights there and some really funny ones, such as “it is better to have a hole than an asshole” (about having the courage to fire a key contributor with an attitude problem).
But if one paid close attention there was also a fascinating pattern. One CEO would say something like “we learned that AB testing really works.” And then a couple of people later, another CEO would say “we learned that building what we ourselves wanted in the product gave us the best results.” Or more starkly put, one CEO learned to do more AB testing and the other to do less. Can both be right?
The answer is yes and it is exactly why startups are hard! You can do too much AB testing and you can do too little AB testing. I have to come to think of this as Scylla and Charybdis problems. And there are a great many of them. You can be too early to a market or too late. You can raise too much money or not enough. You can hire too fast or too slow. You can spend too much time on corporate culture or not enough. And so on. Navigating between the two is hard and also means that someone else’s lesson may not apply to you!
The challenge to find the right course will become a new mini series here on Continuations. I will pick one of these and explain how you can go wrong on either side. Please let me know your own favorite examples to be included in this.

No comments yet