Time Driven Development
summary
Argues for choosing architecture by expected future change vs immediate value, showing concrete results: using Laravel, a CRM then migrated to a local MySQL with a repository pattern and service-provider bindings, the full storage switch initially costs 30 working days but with abstractions takes five days (≈ sixfold speedup). Contrasts an overbuilt factory for version control that sat unused—would have been replaced by a GitHub package in 10 minutes—and cites a simple index.php $2,000/day case to show context matters.
AI-written summary · about
chapters (10)
- 0:00Start
- 4:25We've created a toxic environment that values the usage of good design practices above creating value for the user.
- 5:35Why Time Driven Development?
- 5:54Example #1: Developers' profiles on Adeva's Platform.
- 13:39How can we save time by improving the code design?
- 15:212. Be mindful about what your program expects.
- 16:50Bind abstractions with concrete implementation
- 19:14Example #2: Integrating Github profiles
- 22:59Is there a better way to do it?
- 27:35Software Design Principles are your tools, not your goals.
related talks
59mSlowdown to Grain Speed: Technical practices that take time but save time.
51mThe astonishing value of speed
34mSustainable Architecture
50mTowards an Evolutionary Architecture
23mMoving Fast with XP
40mMove Fast and Ship Things
53mKeynote: Value Driven Development - Maximum Impact, Maximum Speed
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas