What You See Is What It Does: A Structural Pattern for Legible Software
summary
Claims a concrete structure called concepts and synchronizations that separates concerns into independent services and declarative event rules, implements a tiny DSL with when/where/then clauses and a TypeScript engine that records JSON action traces, and evaluates it by reimplementing the RealWorld benchmark among the hundreds of existing variants. Reported benefits are clearer incrementality, integrity, transparency; documented tradeoffs are a thin JSON-only integration channel, duplicated precondition context, and no RPC or rich typing.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:04Collaboration goals
- 2:09Concepts as building blocks
- 3:54Conflated concerns problems
- 5:19Defining concepts by purpose
- 7:47Concept design vs OOP
- 8:51Previous structuring attempts
- 9:56Routing challenges in microservices
- 10:41Pre/postconditions in social media
- 13:32Scattered sync logic problem
- 14:14Introducing synchronizations
- 15:57Sync simplifies behavior
- 16:42Implementation of concepts and synchronizations
- 17:45Legibility through integrity
- 19:52Confidence and creativity
- 20:34Drawbacks of decoupling
- 21:16Concepts as collaborative language
- 22:17Conclusion
- 22:43Q&A case studies
- 24:28Q&A sync scalability
- 26:52Q&A classroom use
