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
NOTE: Excerpts from World After Capital will resume next Monday
We just returned from a wonderful week skiing. One of our family traditions is to all work together completing a puzzle. It’s a fun activity that involves a surprising amount of teamwork, such as finding pieces that belong in a part of the puzzle someone else is working on and trading off working on different areas.
We had always picked 1,000 piece puzzles. This time we wound up buying a 3,000 piece puzzle. After all, how much harder could it be? Well, a lot harder as it turns out. As a rough approximation nearly 10x as hard!
Here is the puzzle in a semi-finished state. That’s as far as we got before the vacation ended, despite spending quite a bit of collective time on it.
There is a good business and life lesson in this. As you add more parts to a problem, the complexity tends to grow explosively. Here are some strategies to combat this problem in business:
Whenever you add a feature, consider removing one that’s used by only a small fraction of users (important caveat: if you have 100x consumers to producers on your service you need to do this analysis separately for each group!)
As you hire employees make sure they are organized into logical units that can work as independently from each other as possible (doing the 1,000 piece puzzles is 3x a 1,000 piece puzzle).
Architect your software so that component services are loosely coupled via APIs.
What’s your favorite strategy for avoiding growth in complexity in business and/or in life?
NOTE: Excerpts from World After Capital will resume next Monday
We just returned from a wonderful week skiing. One of our family traditions is to all work together completing a puzzle. It’s a fun activity that involves a surprising amount of teamwork, such as finding pieces that belong in a part of the puzzle someone else is working on and trading off working on different areas.
We had always picked 1,000 piece puzzles. This time we wound up buying a 3,000 piece puzzle. After all, how much harder could it be? Well, a lot harder as it turns out. As a rough approximation nearly 10x as hard!
Here is the puzzle in a semi-finished state. That’s as far as we got before the vacation ended, despite spending quite a bit of collective time on it.
There is a good business and life lesson in this. As you add more parts to a problem, the complexity tends to grow explosively. Here are some strategies to combat this problem in business:
Whenever you add a feature, consider removing one that’s used by only a small fraction of users (important caveat: if you have 100x consumers to producers on your service you need to do this analysis separately for each group!)
As you hire employees make sure they are organized into logical units that can work as independently from each other as possible (doing the 1,000 piece puzzles is 3x a 1,000 piece puzzle).
Architect your software so that component services are loosely coupled via APIs.
What’s your favorite strategy for avoiding growth in complexity in business and/or in life?
No comments yet