Concept-Centric Software Development: An Experience Report
summary
Palantir restructures development around a centralized concept glossary that records ~300 active users, ties concepts to components across ~2,000 git repos and ~1,300 contributors, and traces evolution with visual concept diagrams and aliases to dereference overlapping terms. The system clusters concepts into concept clusters/aspects, integrates them into planning and docs, resists formal perfectionism, and aims to autogenerate code representations; adoption reaches ~40–50% of component owners but full organization-wide uptake remains unfinished and Alloy was not adopted.
AI-written summary · about
chapters (11)
- 0:00Concept-centric development intro
- 3:56What are concepts
- 8:05Concept dynamics over time
- 11:58Formal glossary at Palante
- 18:17Steps to maintain glossary
- 22:34Recap and future potential
- 23:15Q&A: Structuring glossary
- 24:41Q&A: Renaming concepts
- 26:47Q&A: Alloy formalization
- 28:14Q&A: Concepts vs DDD
- 30:21Closing remarks
related talks
01h 24mA new modularity for software
19mPlatform Design & Content Strategy
19mYou've Built a Design System - Now What?
15mTaming software sprawl and demystifying your distributed architecture (PRT032)
53mSoftware Design: Beyond Boxes & Lines
52mLeaning Into Design Systems
21mEveryone's still eating: building Notion's design system
29mDesign to Code: Roundtable discussion with Code Connect users