Bruce Lee Driven Development

on YouTube ↗39m

" summary

Claim: apply Jeet Kune Do rules to architecture as Bruce Lee Driven Development by treating code like a changing fight. Concrete rules: begin at the core, recognize incremental value, use the simplest most direct approach first, accept change and experiment. Examples: inspects real codebases (Redmine, Laravel/Symfony projects), contrasts UML/abstract models with room/floor/room designs, iterates skateboard→bike→motorcycle to show incremental delivery. Outcome: lightweight, testable iterations that actually deliver usable value.

AI-written summary · about

" chapters (8)

1. 0:00Start
2. 2:30Alan Kay
3. 10:43Purpose of a Library
4. 25:02Bruce Lee Driven Development
5. 25:43Tackling Complexity in the Art of Software
6. 27:22Recognize the Value
7. 30:22Use the Simplest Most Direct Approach First
8. 32:03Change Is Inevitable

" related talks

• 42mKeynote - Livable CodeSarah Mei · RailsConf 2018
• 39mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC Oslo 2018
• 53mIntentional Code - Minimalism in a World of Dogmatic DesignDavid Whitney · NDC Oslo 2023
• 17mThe Way of The Software CraftsmanVitaliy Kulikov · JDD 2018
• 38mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC London 2019
• 30mFrustration Driven DevelopmentEvan Light · Ruby Midwest 2013
• 31mThe Effective Developer - Work Smarter, Not HarderSven Peters · Jfokus 2021
• 33mSet Design: Putting the "Art" in "Architecture"Betsy Haibel · RubyConf 2017