Development: New vs Ready-Made
summary
Discussion of why developers often build new in-house solutions instead of using existing libraries or products, focusing on factors like extra dependencies, need for specificity, scaling issues, difficulties working with open source, perceived 'free' cost, licensing limits, and upgrade burden. The presenters analyze pros and cons of reinventing components (the "bicycle-building"), and when creating new software is appropriate versus when to reuse ready-made solutions.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:55Bikeshedding in development
- 8:02Ready-made solutions analysis
- 15:27Forks and patches
- 19:44When to build your own
- 24:01New vs ready-made
- 30:19Team decision process
- 32:47Limiting solution features
- 38:27Summary and Q&A
related talks
46mBuild, buy, or use open source? All your answers in one chart
52mFinding the Beauty in the Digital Brick
36mCommunities Around a Technology: Why Being Free Is Not Enough
44mLies we tell ourselves about developer infrastructure
27mDependency hell - Or, Developers' perception of software dependencies
31mTips for Library Development (from a Startup Developer)
23mThe developer experience gap
23mDevelopers, start designing!