Originally written in French. Translated by AI — the meaning has been preserved, not the prose.
Short definition
An organization of product work in which the code repository holds the rank of source of truth, and where the other artifacts — specification, changelog, support documentation, design system — are rebuilt from it rather than maintained alongside it.
Full definition
The phrase circulates in technical teams' vocabulary to designate practices where the repository centralizes what used to live elsewhere: documentation as code, infrastructure as code, versioned configuration. It describes a tooling choice there, internal to engineering.
In the articles on this blog, it designates a way of working and not a technical architecture. What characterizes it isn't that the files are in the repository, it is the direction of production: you start from the real code to obtain the product artifacts, instead of starting from the artifacts to obtain the code. The Product Manager is concerned first and foremost, since it is their deliverables whose mode of manufacture changes.
The term presupposes two conditions, and it is used wrongly when they are missing: a repository legible enough that something other than behaviour can be extracted from it, and effective access to that repository by those who produce the artifacts.
Usage in the field
Used to qualify a chain of artifact production, and to situate what changes in a Product Manager's work when code becomes the raw material rather than the end point.
Synonyms and variants
"Code as the source of truth", used when the emphasis falls on rank rather than on the organization of work.
Not to be confused with
- Source of truth — Source of truth — the artifact that prevails in case of disagreement. Code centric is the organization that follows from choosing code as the source of truth; the rank can be recognized without anything being organized around it.
- Documentation as code — the practice of storing and versioning documentation in the repository, under the same control as code. Documentation there is still written by hand, it only changes location.
- Code is Law — Lawrence Lessig's formula about how technical architecture imposes rules on usage. It bears on the normative power of code, not on the manufacture of artifacts.
Examples
"Code is no longer only the final deliverable: it becomes the central element, the source of truth around which the product's other artifacts orbit and from which they are rebuilt, in a genuinely code centric logic."
"Code centric isn't a technical concept — it's a way of working that redefines the product manager's place in the value chain."
Ambiguities / debates
The word suggests a total centralization that isn't intended: Figma and Zendesk stay relevant in their domain, the approach changes their position in the chain without replacing them. The disagreement bears on the extent — how far an artifact can be regenerated before losing what the repository doesn't contain, that is, intention.