Code as a Product
summary
CARTO engineers describe treating code libraries as products: they explain building frontend libraries that leverage the CARTO Location Intelligence platform, managing version lifecycles, publishing processes, and developer onboarding. They also cover collecting customer feedback, common mistakes, and how library product management differs from regular consumer products.
AI-written summary · about
chapters (19)
- 0:00Code product introduction
- 1:04Product design cycle
- 4:20irSi library example
- 8:10Launch and initial feedback
- 9:56Retreat to refocus library
- 14:27Product activities in code
- 15:11Problem discovery and selection
- 17:38Product definition and design
- 19:04Fake tutorials for validation
- 21:32Internal hackathons
- 23:40Developer user testing
- 25:06Product communication and adoption
- 26:09Documentation importance
- 26:50Why document code
- 27:57Required documentation types
- 31:24Six docs tips
- 34:53Versioning and changelog
- 37:45Team release process
- 38:28Q&A
related talks
40mCode is your partner in thought
42mSoftware Architecture vs Code
47mDeveloping a digital product. What it is and how
45mAgentic Coding, the New Frontier of Platform Engineering
16mCode is Cool Products are Better
06mPlatform Engineering with a Product Management Mindset: 10x Your De...
31mMaking sense of frontend code with forensic techniques
36mApplying Product Thinking to internal infrastructure