DCI: semiotics applied to software
summary
Argues that DCI maps semiotics to software by treating data as symbols, context as rules and interaction as meaning, claiming this narrows the gap between user mental models and code. Shows a working API built with grape and Roar (a public-transportation lines-and-stops service), reports adding new resources takes minutes after ~two to three hours of initial structure work, and notes dynamic role-mixing hurts performance so use delegators/decorators instead of always extending objects at runtime. Presents a small gem called graBine that scaffolds DCI-style routes, contexts and decorators.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:18Semiotics basics
- 8:25Introducing DCI pattern
- 10:57DCI in software architecture
- 13:49DCI benefits and performance
- 15:36Semiotics and DCI connection
- 18:55GraBine RESTful API
- 24:00Live GraBine demo
- 30:49GraBine micro framework
- 31:56Design patterns and problem-solving
- 33:00Summary
related talks
47mIntroduction to object-oriented programming for those who have never done it before
59mSondheim, Seurat and Software: finding art in code
43mLanguage Games
21mDataEngBytes 2023 - SYD-T3-04 - Abhinav Goyal
37mBuilt to last: A domain-driven approach to beautiful systems
23mMastering visual communication for software development
20mInvisible Design Systems
21mDoodle-Driven Development