On Parenthood, Systems Thinking, and App Development
summary
Claim: applying systems thinking from early parenthood reduces app entropy by designing for inevitable change. Concrete tools and patterns include Ember modifiers for legacy jQuery, Ember Data adapters and serializers, iterative pivots instead of rigid rules, and explicit escape valves to contain failure. Example: ditching elaborate recipes in favor of swappable meals is treated as a successful iteration that preserves goals. Result: systems evolve, optionality and context at all levels make long-lived apps easier to maintain.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:16Parenthood as adaptation
- 2:40Unintended systems
- 4:28Flexibility and iteration
- 5:31Embracing change
- 7:16Contextual awareness
- 9:01Shared mental models
- 10:47Ember as foundation
- 12:10Refining systems
related talks
27mDesigning Even Larger (JavaScript) Applications
31mBest Practices for Architecting Server-Driven Web/Mobile Apps
30mIt's About Systems
27mOn the Development of Reactive Systems with Ember.js
40mBuilding resilient frontend architecture
58mImmutable Patterns of System Design; From Monolith to Agentic AI
40mDevelopment Strategies for a 14-Year-Old Android App to Survive a Generational Design Shift
33mApp Architecture: Faster, Better... Simpler