Manifest-Driven Development
Manifest-Driven Development (MDD) is a software methodology that uses a central manifest file to define project structure, dependencies, and build processes. This approach aims to improve project clarity and automation by making the manifest the single source of truth for development workflows.
Background
- The piece critiques a pattern in software/tech where teams adopt rigid "manifestos" (like the Agile Manifesto, The Phoenix Project's principles, or various "x-driven development" methodologies) as dogma, substituting genuine critical thinking with allegiance to a set of written tenets.
- A "manifesto" in tech typically refers to a short, authoritative document outlining core values and principles — meant to guide practice, but often ends up being followed to the letter rather than in spirit.
- The author argues this leads to cargo-culting: teams repeat the rituals of a methodology (stand-ups, sprints, retrospectives) without understanding why they exist, undermining the original intent.
- Underlying context: the broader software engineering field has long debated "methodology wars" (Waterfall vs. Agile, Scrum vs. Kanban), and this piece positions itself as skeptical of any approach that treats a written document as an infallible source of truth.
- "Manifest-Driven Development" is a satirical coinage, playing on terms like Test-Driven Development or Domain-Driven Design to highlight blind adherence.