This talk is about using simple values (as opposed to complex objects) not just for holding data, but also as the boundaries between components and subsystems. It moves through many topics: functional programming; mutability's relationship to OO; isolated unit testing with and without test doubles; and concurrency, to name some. The "Functional Core, Imperative Shell" screencast mentioned at the end is available as part of season 4 of the DAS catalog.
When Does a Specification Become a Program? - The Phoenix Architecture
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?
Andrew Kelley: A Practical Guide to Applying Data Oriented Design (DoD)
convex.dev
All gas, no breakages. Convex is the reactive backend platform that keeps up with you and your agents.
Towards infinite context windows: neural KV cache compaction | Base Labs
Working to advance and democratize open-source intelligence.
Addressing the Precision-Breadth-Simplicity Impossible Trinity in Psychological Research: A Comprehensive Exploration Approach
Psychological research faces a fundamental challenge—the Precision-Breadth-Simplicity (PBS) impossible trinity. While experimental findings are often precise and simple, they tend to be narrow in scope. Conversely, broad-and-simple concepts frequently lack precision. Developing theories that are both precise and broad is scientifically valuable but inevitably introduces complexity, which conflicts with humans’ cognitive limitations in processing complexity. To address this impossible trinity, I propose a comprehensive exploration (CE) approach—a data-guided theory-building framework that involves: (1) designing experimental conditions in a stimulus-driven way, with minimal upfront theoretical specification; (2) conducting experiments with tens of millions of observations (e.g., 40 million responses in Huang, 2025a); (3) modeling the results through iterative improvements; and (4) producing the outcome: a moderately complex quantitative information-processing model to integrate diverse empirical findings. Inspired by similar strategies that drove breakthroughs in artificial intelligence (e.g., ImageNet’s role in advancing object recognition), the CE approach offers a promising path toward more integrative psychological theories. Initial implementations in visual working memory research demonstrate both its practicality and potential to transform how we study mental processes.
Resilient Data Futures — Discourse Graph
A living, content-addressed, contributable form of the SciOS Resilient Data Futures whitepaper.
Resilient Data Futures — Discourse Graph
A living, content-addressed, contributable form of the SciOS Resilient Data Futures whitepaper.
Resilient Data Futures — Discourse Graph
A living, content-addressed, contributable form of the SciOS Resilient Data Futures whitepaper.
Resilient Data Futures — Discourse Graph
A living, content-addressed, contributable form of the SciOS Resilient Data Futures whitepaper.
In policy circles I keep hearing about "horizontal" and "vertical" interoperability, notions that I haven't encountered in tech standards. I sat down to write about why it's a limiting understanding of interoperability and how we can do better. berjon.com/interoperability/
The Direction of Interoperability
berjon.com"Teams working across organizational boundaries, sharing structured data, and building on each other’s work with ease." I know it's called "adversarial interop", but it actually feels like "community interop", at least right now
Toni Schneider
Conference Takeaways I’m back from ATmosphereConf in Vancouver, and I'm processing what I saw and heard. The atproto developer community could not have been nicer and more welcoming. Here are some takeaways. ... toni.org/2026/04/03/conference-takeawa…
I've been exploring permissioned data spaces technology and components, thinking about what the end-result is going to look like. @dholms.at's last dev diary has some good nuggets and I decided to jump into an ECMH implementation.
ngerakines.me/ecmh-rs
tangled.orgThe smallest permissioned data shape: a bookmarks space with a member list that never grows past me. Same bookmark record the atmosphere already uses, same write path, different address. URIs, scopes, tokens, and the full credential flow inside.
Permissioned Data Shapes: Self-Only Bookmarks
ngerakines.leaflet.pubprivate data unconf session at #atmosphereconf is packed really great to hear about the different approaches, use cases, concerns we don't have great language for describing topology and trade-offs in distributed architectures the "what is where, and why" often feels untangling vs compositional
AT Protocol Spaces explainers
Search terms: ATProto Spaces, permissioned data, buckets
Permissioned Data Shapes: Self-Only Bookmarks - Nick's Blog
The Atproto Spaces Alpha is Live - AT Protocol
Reintroducing Spaces - Daniel's Leaflets
Permissioned Data Diary 1: To Encrypt or Not to Encrypt - Daniel's Leaflets
