Evidence-Based Software Engineering vs Guesswork Based Development
Developers should learn and use EBSE when working on complex or high-stakes projects where decisions impact cost, safety, or performance, as it helps mitigate risks by relying on proven methods rather than assumptions meets developers should avoid guesswork based development as it contradicts modern software engineering principles like agile, devops, and data-driven decision-making. Here's our take.
Evidence-Based Software Engineering
Developers should learn and use EBSE when working on complex or high-stakes projects where decisions impact cost, safety, or performance, as it helps mitigate risks by relying on proven methods rather than assumptions
Evidence-Based Software Engineering
Nice PickDevelopers should learn and use EBSE when working on complex or high-stakes projects where decisions impact cost, safety, or performance, as it helps mitigate risks by relying on proven methods rather than assumptions
Pros
- +It is particularly valuable in industries like healthcare, finance, or aerospace, where software failures can have severe consequences, and in research or academic settings to advance the field through rigorous study
- +Related to: empirical-research, systematic-reviews
Cons
- -Specific tradeoffs depend on your use case
Guesswork Based Development
Developers should avoid Guesswork Based Development as it contradicts modern software engineering principles like Agile, DevOps, and data-driven decision-making
Pros
- +It might be used in rare, high-pressure scenarios with tight deadlines or limited resources, but even then, it's recommended to apply minimal viable practices like quick prototyping or heuristic-based estimation instead
- +Related to: test-driven-development, agile-methodology
Cons
- -Specific tradeoffs depend on your use case
The Verdict
Use Evidence-Based Software Engineering if: You want it is particularly valuable in industries like healthcare, finance, or aerospace, where software failures can have severe consequences, and in research or academic settings to advance the field through rigorous study and can live with specific tradeoffs depend on your use case.
Use Guesswork Based Development if: You prioritize it might be used in rare, high-pressure scenarios with tight deadlines or limited resources, but even then, it's recommended to apply minimal viable practices like quick prototyping or heuristic-based estimation instead over what Evidence-Based Software Engineering offers.
Developers should learn and use EBSE when working on complex or high-stakes projects where decisions impact cost, safety, or performance, as it helps mitigate risks by relying on proven methods rather than assumptions
Disagree with our pick? nice@nicepick.dev