You Are the Storyteller: what fairytales can teach us about frontend development
summary
Argues that treating code as a story reduces surprises and improves handoffs: use docs as hook plus clear why statements, incremental tests, and a design system to reveal complexity slowly; show that writing small readable components, then refactoring and enforcing patterns through code review and CI actually prevents regressions and eases maintenance, so the built outputs—documented components with tests—work in production and lower bug counts.
AI-written summary · about
chapters (15)
- 0:00Storytelling and fairytales intro
- 2:22Why stories captivate brains
- 3:26Fairytales reveal lessons
- 4:32Little Red Riding Hood insights
- 7:52Code smells and pitfalls
- 9:00Best practices from history
- 10:27Understanding task purpose
- 11:34Knowing your audience
- 12:58Code as narrative
- 14:24Detail versus readability
- 15:49Consistency and design systems
- 16:56Refactoring like editing
- 18:01Learning from feedback
- 18:42Rewriting mistakes
- 19:05Better storytellers
related talks
44mCooking up Better Front-end Applications with Inspiration From the Culinary World
56mThe Web, Its Frameworks and Its Standards: Deconstruct to (Re?)Construct
40mBuilding resilient frontend architecture
35mMicro-Frontend & Me, a love story
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale
35mTesting in Frontend World
44mBuilding resilient frontend architecture
01h 01mDesign Principles for Better FrontEnd Code