My favorite verbose programming technique
summary
Claim: use sequence-based enumeration to turn event-driven requirements into an executable state machine so specification and implementation are the same. Shows an APL spec for a security alarm with nine canonical sequences, a stochastic tester that generates fuzz cases from the spec, and a parser spec that grows to three to four hundred pages and finds real bugs. Uses low-overhead tables plus stimuli abstraction to control state explosion, compiles to efficient code, and underlies demo apps (a Galaga-like and a spreadsheet) that work.
AI-written summary · about
chapters (10)
- 0:00Verbose programming intro
- 3:08Event-driven in APL
- 10:33APL as executable spec
- 17:37Clean room inspiration
- 22:09Security alarm demo
- 31:06Sequence enumeration in APL
- 44:47Benefits and limitations
- 50:22State equivalence handling
- 53:11Adoption in systems
- 57:21Q&A
related talks
42mSurprise yourself with Property Based Testing
59mstd variant and the power of pattern matching
59mFunctional Programming: data
44mTyped Design Patterns for the Functional Era
01h 27mDeclarative thinking, declarative practice
37mA (Not So Gentle) Introduction To Systems Programming In ATS
38mEngineering Software Integral Types
24mLeveraging State Machines to Build Operators in Rust