Time Driven Development
summary
Argues for choosing design effort by expected lifetime and change rate: an early prototype uses Zoho CRM and a single class API to ship, then later swaps to MySQL migration by adding Eloquent models, a repository interface and one service-provider binding so controllers stay unchanged; contrasts a year-long factory for GitHub/Bitbucket that never gets used with a ten-minute API integration. Claims time invested up front must be justified by real future needs.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:40Why Time Driven Development?
- 6:05Example #1 Adeva Platform: Building developers' profiles.
- 11:19How can we save time by improving the code design?
- 11:39Don't depend on concrete implementations.
- 13:00Be mindful about what your program expects.
- 14:34Bind abstractions with concrete implementation.
- 23:03Software Design Principles are your tools, not your goals.
related talks
37mHow I Accidentally Wrote the Best Code of my Career
39mWhat is Performance Driven Development and why aren't you doing it?
40mBarely Enough Design
41mLiving the Best Life on a Legacy Project
31mLearn to appreciate legacy
38mIntroDDDuction
37mLearn to appreciate legacy (Story about Zed)
44mBuilding a complex product while scaling a team and a business on Laravel