Retaking Rules for Developers
summary
Argues for treating rules as a host-language control structure rather than a business-only DSL, combining functional ideas with a production-style engine: uses Clara rule engine in Clojure/ClojureScript, implements unification, truth maintenance, and composable rules, produces immutable sessions that share state efficiently and profile similarly to Drools, and generates and serves explainable rule visualizations that trace why facts fire. Demonstration shows code-as-data rule definitions, ability to retract by equality, a small web prototype that renders provenance, and practical reuse inside ordinary functions.
AI-written summary · about
chapters (13)
- 0:00Intro
- 7:30Expert Systems
- 9:21Rule authoring
- 12:00Rule automation
- 13:20The proven model
- 14:45Unit of logic
- 16:01Arbitrary actions
- 16:31Nulls
- 17:00Clojure
- 19:03Code
- 23:38In Action
- 29:01Explainability
- 31:27Knowledge
related talks
54mKotlin DSLs as a Single Source of Truth for Multiple Tasks
55mTransforming Enterprise Development With Clojure
30mBeginner Driven Development
45mResidential Programming without Mutable State
57mCore Software Design Principles for Programmers
15mManipulating GUI Structures Declaratively
15mLive Programming a Live Programming Environment: An Experience Report
33mStop Debating. Start Enforcing with Lint Rules