Continuous Obsolescence
This anti-pattern is known for developer failing to catch up the current version of the software / finding the dependencies to create a product release.
Consequences
Consequences
- Customer suffers dependencies hell when using the product.
- Customer uses old or outdated codes/library.
Symptoms
Symptoms
- When the library has released but the product specification is still using the legacy version.
- When the commercial product quickly obsolete the older version so that the newer product sells faster and greater.
Causes
Causes
- In-balance between commercial gain vs. mind-share.
Fixing Recipes
Fixing Recipes
- Participate in open systems standards, joint-marketing initiatives.
- Find a balance between chaotic new technology vs. stable legacy technology.