Behavioral Programming: Aligning Code with How We Think -
summary
Behavioral Programming uses parallel B-threads that request/wait/block sync points and an event‑selection engine so new behavior is added as separate modules instead of editing existing code. Example: a multiple‑of‑3 checker stays untouched while an added B‑thread enforces “ends with 5,” and the event trace resolves outputs (6 → good, 5 → bad) without changing the original function. Researchers prove a smaller reachable state space and a small study with high‑schoolers favors BP; tradeoffs include harder unit testing and potential tangled threads. add new behavior as separate B-thread
AI-written summary · about
chapters (7)
- 0:00Introduction and passion
- 3:54Deep dive into behavioral programming
- 17:44How we think about complex systems
- 24:59Requirements vs implementation worlds
- 37:31Brain analogy and natural programming
- 41:02Trade-offs and future of the paradigm
- 47:55Q&A session
related talks
01h 02mProcedural Programming: It Never Went Away
51mTechniques for Wielding Data and Behaviors
01h 24mProcedural Programming: It’s Back? It Never Went Away
15mBehavior Trees in Action: A Study of Robotics Applications
44mBehavioral Software Engineering
50mSoftware Is Details
01h 00mEngineering Software
47mBEAM Architecture Handbook