#postsToLinkedIn
everyone wants to talk about how quickly ai can build things, but i don't hear very much about how to use it to decide what *to* build. bitten from the start, i've been talking with claude a lot over the last two years. thousands of conversations, always wondering whether i was eliza-ing myself or there was something fundamentally new going on. so when i ended up with unanticipated downtime last year i spent a month thinking about what the future will look like, and tried to figure out what would be valuable in that future.
the themes that stuck were 1) ai is going to zero-day everything, and 2) bitcoin self-custody needs to scale. huge problems, but real ones. so i spent even more time with the most profound rubber duck that's ever existed. threw spitballs at the ceiling, pasta at the wall. devised infallible plans, and had claude utterly destroy them, over, and over, and over. had claude defend them while i poked holes. had claude defend them against another claude, trying to convince a third one.
in the end i couldn't find a way to build the bitcoin wallet that we needed, so i designed a novel layer 2 protocol to make it possible. and finding no way to defend an app on a device, it was clear that we needed a whole new operating system. neither of these are conventionally possible for one person. not even for one team. certainly not in one year.
but by now you already know how this ends. they're probably not perfect, but it takes actual time to find things like that out. the lesson is to build with ai, but don't just build: think different
bitcoin layer 2:
https://github.com/bitcoin-deposits/deposits
lisp os:
https://github.com/ynniv/modus