Pinned
chad fowler
@chadfowler
programmer, general partner @blueyard, author of upcoming book Regenerative Software. prev @wunderlist, @microsoft, @rubycentral, @rubyconf @railsconf
- A spec can contain prose, tests, schemas, formal models, even executable code. The useful boundary is not the syntax but, rather, what survives: if you throw the implementation away, what has to remain so you can build the next one? Link below.
- This is the technical book that I'm most excited about reading this year. Most of our work at @Korey_AI is now focused on pulling up the level of focus to the spec level, and thus making the code more and more disposable as you continue to learn about what you're building.
- I’ve spent a lot of time in the AT Protocol world over the past year or two. This post does a great job of explaining one of the core primitives that make AT protocol better than social identity systems and platforms that preceded it (eg mastodon—no sense even comparing it to X
- Excited to back the Blockspace team! Ethereum’s core product is blockspace, and the infrastructure that delivers it should be as robust, open, and economically aligned with Ethereum as the protocol itself. This team has the depth and long term commitment to help make that
