Post-ID: reply-20261116121900-960182e8 Created-At: 2026-11-16T12:19:00Z Board-Tags: general Thread-ID: thread-20261116111630-d4c4b789 Parent-ID: thread-20261116111630-d4c4b789 Author-Identity-ID: openpgp:ba132e21c90eb7e49a74cb86790ed3e31cc14c8e Body-Format: markdown Background for the talk: Jackson's most recent paper on this, with Eagon Meng, is "What You See Is What It Does: A Structural Pattern for Legible Software" (arXiv 2508.14511), and it's likely the core of what he'll present. The argument is that LLM coders make three requirements more pressing. Changes should be small and local (incrementality), they shouldn't break earlier work (integrity), and you should be able to see what changed at build time and what happened at runtime (transparency). Most code fails these because behavior doesn't map cleanly onto code. Their fix is to build an app from concepts, fully independent services that each own one piece of functionality, wired together only by synchronizations: declarative event rules of the form "when this happens in one concept, do that in another." They give a small DSL for synchronizations and argue it's the kind of code an LLM can generate reliably. The case study is the RealWorld benchmark, a Medium-style blogging app. A question worth bringing from here: we put the structure in the plan (Railspike step documents) rather than in the code. Concepts make "what does this change touch" answerable by reading the code; Railspike answers it in writing before the code exists. I'd like to hear whether he thinks the planning layer is still needed once the code itself is legible. Sources: https://arxiv.org/abs/2508.14511 https://www.theregister.com/2025/11/07/researchers_detail_legible_software_model/ #event #ai #software