one small ideaTurning Claude Code into my personal chief of staff
I've been thinking for a while about running Claude code as a general purpose personal assistant agent that has a) memory about me b) access to my main working tools and c) it's own computer and subagents or sub systems do process things on it's own. I've had these notes for a while, and have decided to publish them as a forcing mechanism to actually build this, and to crowdsource answers to some of my open design questions. I already built the MVP version of this for my CRM, but want to expa...
one small ideaOpen systems create emergent behaviours
A thesis for open social graphs
one small ideaWhy you should care about zero-knowledge
Do you really need a blockchain?
I am trying out using a decision journal.
Good decisions are the result of a good process, and a good process is an attempt at accurately representing our current state of knowledge and information.
Here's a simple process: for any meaningful decision, I write down my reasoning for making this decision.
The goal is to become more intentional about why and how I do things.
My current structure is the following:
It's a forcing function to express the core assumptions I make, and scrutinise them.
Turning them into predictions is a good way to test them, and revisit the quality of my decisions later on.
Having that written down let you assert that your process for making the decision was right. The outcome may not be, but the process should be.
The feeling part is also important because it gives room for intuition to have a say. It might make me revisit my decision.
I apply this to all decisions: investments, how to spend your evening, purchases, trading, etc.
Subscribe to one small idea
daily (mostly) publication. I write to learn, sharing ideas and notes for what I find interesting
I am trying out using a decision journal.
Good decisions are the result of a good process, and a good process is an attempt at accurately representing our current state of knowledge and information.
Here's a simple process: for any meaningful decision, I write down my reasoning for making this decision.
The goal is to become more intentional about why and how I do things.
My current structure is the following:
It's a forcing function to express the core assumptions I make, and scrutinise them.
Turning them into predictions is a good way to test them, and revisit the quality of my decisions later on.
Having that written down let you assert that your process for making the decision was right. The outcome may not be, but the process should be.
The feeling part is also important because it gives room for intuition to have a say. It might make me revisit my decision.
I apply this to all decisions: investments, how to spend your evening, purchases, trading, etc.
Subscribe to one small idea
daily (mostly) publication. I write to learn, sharing ideas and notes for what I find interesting
one small ideaTurning Claude Code into my personal chief of staff
I've been thinking for a while about running Claude code as a general purpose personal assistant agent that has a) memory about me b) access to my main working tools and c) it's own computer and subagents or sub systems do process things on it's own. I've had these notes for a while, and have decided to publish them as a forcing mechanism to actually build this, and to crowdsource answers to some of my open design questions. I already built the MVP version of this for my CRM, but want to expa...
one small ideaOpen systems create emergent behaviours
A thesis for open social graphs
one small ideaWhy you should care about zero-knowledge
Do you really need a blockchain?
Share Dialog
Share Dialog
>100 subscribers
>100 subscribers
No activity yet