A new modularity for software
summary
Proposes a practical modularity where user-facing "concepts" are the unit of design: each has a purpose, structure, actions and an operational principle. Demonstrates the idea by reworking git into getless, building a DejaVu platform of reusable concept cliches that stitch front end and back end with a gateway for transactional synchronization. Reports a catalog of ~30 concepts, reproduces multiple 25-person-week student apps from those cliches, and shows specific design rules (singularity, uniformity, generosity, integrity) that identify real misfits and fixes.
AI-written summary · about
chapters (40)
- 0:00Intro
- 2:14a simple task: sign and return
- 3:04acrobat to the rescue?
- 4:53adobe lightroom: easy cropping
- 6:28what's the essence of the problem?
- 7:51adobe fixes acrobat
- 8:47apps characterized by their concepts
- 9:42app classes characterized by concepts too
- 11:02the conventional view
- 11:38concepts are invented, not just out there
- 12:46concepts have purpose
- 14:16concept structure is designed not discovered
- 15:44concepts are reusable
- 17:04explaining concepts
- 20:19when concepts don't fulfill purpose
- 22:38concepts: modules of behavior
- 23:41the style concept
- 24:37a research & teaching program
- 27:40category tab settings
- 29:54what you can't do
- 32:04image quality setting
- 32:39aspect ratio
- 33:04image size setting
- 33:44non-standard ratio + raw?
- 34:48what's a font?
- 36:21introducing a concept
- 37:07what's going on?
- 38:11one-to-one mapping
- 40:17four ways to fail
- 41:54overloading fuji camera
- 42:38overloading epson driver
- 44:22overloading email subject
- 46:57the uniformity rule
- 51:55the genericity rule
- 55:41interpreting composite behavior
- 56:02the integrity rule
- 56:34the label concept
- 56:59conversation breaks label
- 58:13reversing the process
- 59:55architecture of deja vu
related talks
31mConcept-Centric Software Development: An Experience Report
46mModular Applications with Spring
53mSoftware Design: Beyond Boxes & Lines
51mModularization: Foundation of Microservices and Monoliths
20mSoftware design
51mDomain-centric? Why Hexagonal- and Onion-Architecture are answers to the wrong question
44mModular Design in Elixir
49mRealizing Domain Design Through Architectural Modularity ...