As Is Software vs Rewrite From Scratch
Developers should use As Is Software when working with mature, stable systems where business continuity is critical, such as in banking, healthcare, or government sectors meets developers should consider a rewrite when the existing codebase has become unmaintainable due to accumulated technical debt, uses obsolete technologies, or has architectural flaws that hinder scalability and new feature development. Here's our take.
As Is Software
Developers should use As Is Software when working with mature, stable systems where business continuity is critical, such as in banking, healthcare, or government sectors
As Is Software
Nice PickDevelopers should use As Is Software when working with mature, stable systems where business continuity is critical, such as in banking, healthcare, or government sectors
Pros
- +It is ideal for minimizing disruption, reducing costs associated with full rewrites, and leveraging existing investments in code and infrastructure
- +Related to: legacy-systems, software-maintenance
Cons
- -Specific tradeoffs depend on your use case
Rewrite From Scratch
Developers should consider a rewrite when the existing codebase has become unmaintainable due to accumulated technical debt, uses obsolete technologies, or has architectural flaws that hinder scalability and new feature development
Pros
- +It is particularly useful for legacy systems where the original design no longer aligns with current business requirements or modern development practices, allowing for a cleaner, more efficient implementation
- +Related to: refactoring, technical-debt-management
Cons
- -Specific tradeoffs depend on your use case
The Verdict
Use As Is Software if: You want it is ideal for minimizing disruption, reducing costs associated with full rewrites, and leveraging existing investments in code and infrastructure and can live with specific tradeoffs depend on your use case.
Use Rewrite From Scratch if: You prioritize it is particularly useful for legacy systems where the original design no longer aligns with current business requirements or modern development practices, allowing for a cleaner, more efficient implementation over what As Is Software offers.
Developers should use As Is Software when working with mature, stable systems where business continuity is critical, such as in banking, healthcare, or government sectors
Disagree with our pick? nice@nicepick.dev