Reusable ideas about the reuse of software
summary
NAV runs about 143,000,000 lines of code across 600 developers and 200 teams and finds speculative reuse failing in practice, so it moves to product-organized reuse with dedicated ownership teams. Built examples include a payment service that centralizes tax and manual handling, a platform called nice that creates a golden path for deployments, and a shared library wonderwall for Norwegian authentication; forks and copy‑paste help briefly but fail long term, so clear product teams, financing and incentives decide whether reuse endures.
AI-written summary · about
chapters (6)
- 0:00Software reuse challenges
- 15:21History of reuse attempts
- 15:43NAV software landscape
- 21:42Reuse patterns
- 42:44Social and technical reuse
- 55:16Key takeaways
related talks
24mHow to tackle the reusability problem in the software industry
57mBuilding a dedicated platform for frontend developers @ NAV
24mManage Your Huge Codebase like a Boss
43mOld code doesn't stink - Refactor or Rewrite
47mReact Native code reuse: Architecture that works
01h 03mMonorepo – How to do frontend faster, better and safer
49mScalable Best Practices for Your Development Team
41mYou Keep Using That Word, I Don’t Think It Means What You Think