You Aren't Gonna Need It...Until You Are?
summary
A joke implementation escalates into FizzBuzz Enterprise Edition spread over 128 files, illustrating how clever abstractions multiply complexity. An open source e‑commerce framework skips pagination for variants, facets, channels and customer groups, then encounters real users with 500–1,000 variants, 3,000 customer groups and 1,600 channels, forcing a breaking major-version change to add pagination. The takeaway: YAGNI saves effort early, but misjudging scale creates costly rewrites—judgment about where to prebuild features is what actually matters.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:57Over engineering problem
- 9:24YAGNI vs PAGNI
- 12:37Judgment in development
- 19:35Senior engineer mindset
- 21:41Conclusion and Q&A
related talks
16mYou Can't Outrun Complexity - But You Can Orchestrate It.
29mFrom big to small and back again
29mApps, Stacks, and Frameworks: Avoiding “Shiny Object” Syndrome
44mWhy "Enterprise Tools" Are Bad for the Enterprise
55mFollowing Google or Don't Follow the Followers, Follow the Leader
26mFeatures Versus Futures
36mApps, stacks & frameworks: Avoiding "Shiny Object" Syndrome
37mHow to Lose Your Feature Bloat?