https://github.com/mattdibi/edd-manifesto
Emergency Driven Development Manifesto
https://github.com/mattdibi/edd-manifesto
agile-development agile-methodologies
Last synced: about 2 months ago
JSON representation
Emergency Driven Development Manifesto
- Host: GitHub
- URL: https://github.com/mattdibi/edd-manifesto
- Owner: mattdibi
- License: mit
- Created: 2025-03-27T18:26:29.000Z (about 2 months ago)
- Default Branch: master
- Last Pushed: 2025-03-27T18:28:38.000Z (about 2 months ago)
- Last Synced: 2025-03-27T19:35:14.785Z (about 2 months ago)
- Topics: agile-development, agile-methodologies
- Homepage:
- Size: 2.93 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# *The Emergency-Driven Development (EDD) Manifesto*
We are uncovering better ways of developing software by constantly putting out fires and thriving in chaos. Through this work, we have come to value:
- **Crisis management** over careful planning
- **Last-minute patches** over sustainable architecture
- **Urgent hacks** over well-thought-out design
- **Blame assignment** over root cause analysis
That is, while we acknowledge that stability, planning, and maintainability have some value, *we prioritize immediate disaster mitigation at all costs.*
### *EDD Principles*
1. *Our highest priority is to deploy fixes immediately*—whether they work or not is a problem for Future Us.
2. *Changing requirements are not just welcome—they are inevitable, because we didn’t anticipate them in the first place.*
3. *Delivering hotfixes frequently* is the primary measure of progress.
4. *Developers and managers must work together daily*, mostly in frantic all-hands calls.
5. *Projects are built around exhausted, overworked individuals* who are expected to sustain an indefinite firefighting pace.
6. *The most efficient form of communication is panicked Slack messages at 3 AM.*
7. *Working software is the primary measure of success—until the next outage.*
8. *Sustainable development is a nice theory, but we prefer the thrill of continuous survival mode.*
9. *Technical excellence and good design enhance agility, but we wouldn’t know—we never have time for either.*
10. *Simplicity—the art of maximizing the amount of work undone—is irrelevant when everything is on fire.*
11. *The best architectures, requirements, and designs emerge from years of accumulated, hastily applied patches.*
12. *At regular intervals, the team should reflect on how to improve their process—but only after the current crisis is resolved (which is never).*
Welcome to EDD, where every day is a new emergency, and nothing is ever really "done"! 🚨🔥