Golden Hammer

This anti-pattern is about locking the project into a particular scope/technology, making less expense to adopt other kind of solutions. Hence, the name golden hammer carries the meaning: one single hammer to get everything done.

Exception

1. When the architecture and feature design is intended (e.g. selected Oracle database for timeless implementation).
2. When the vendor suite provides the software needs.

Consequences

• Every projects use the identical tools and that's it.
• Solution has inferior performance, benchmark, and scalability across industry.
• System architecture is best described by vendor tool-sets.
• Developers became isolated from industry.
• Deter technical growth horizontally.

Symptoms

• A universal tool solving every problems.
• Reliance on an unreliable, unstable, readily available technologies.

Causes

• Several proven successes using the same approach.
• Large investment in training/gaining experience in product and technology.
• Group is isolated in industry.
• Reliance of vendor lock-ins technologies.

Fixing Recipes

1. Re-plan resources for growth commitment from management.
2. Consistently explore, test, and experiment new technology.
3. Develop mitigation plan for vendor lock-in type technologies.
4. Refrain from using the same solution. Always explore at least 2-3 types of different solutions and technology and review each of their performance.