Drawing the line between 3rd party and handcrafted code
summary
Argues for concrete decision rules: measure impact not hype, use a VS Code size plugin and Webpack Bundle Analyzer, check minified + gzipped size and dependency graph, prefer a library that solves ~80% of the problem, and avoid premature rewrites. Gives heuristics—pick the first and iterate, deep source inspection when needed, or roll your own only when control outweighs maintenance cost—and names Moment as an example being ~3MB to justify cautious choices.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:58Glenn Reyes
- 8:21Architectural Decision
- 8:58Size Bugs Dependency Documentation Time Constraints Development Environment License
- 13:17Community Support
- 14:27People love solving problems
- 15:02How are problems solved in web development?
- 16:20Look into the source code
- 17:48Dealing with picking the most popular library
- 20:38Understand the importance of decisions
- 21:02Try to get the best outcome but reduce potential risks
- 22:35Take risks and keep moving forward
related talks
24mDrawing the line between 3rd party and custom code
24mThe missing guide for deciding between 3rd party library and custom code -JSWORLD 2023
06mLightning talk from Andrey Sitnik
26mGood Code
53mIntentional Code - Minimalism in a World of Dogmatic Design
44mLies we tell ourselves about developer infrastructure
50mIntentional Code - Minimalism in a World of Dogmatic Design
35mKnowing Your TCO (Total Cost of Ownership)