Silver bullet anti-pattern

I will continue my little serie about anti-patterns of decisions and activities that may screw up projects and make developers (and why not also others) life hell. Now let's look at silver bullet anti-pattern. It is about using unknown tools and technologies in the place where one shouldn't never do that.


NB! This blog is moved to

Click here to go to article


  • I agree. We may think that technical decisions are always the programmers responsability but has you has described they are not always the ones that should decide.

    The project manager should see the high risk involved in accepting a major change like this one and inform the stakeholders. Technology is not important. What it is important is to build a software solution to solve a real world problem.

  • The guy introducing the new texh in your scenario sound like a case of "Drive-By Architecture".

    "This product does 90 percent of everything we need, lets use it".

    The reply : "Sure, but it only does the easy 90 percent, its that last 10 percent that we need help with"

  • Thank you Andrew for a good point. One thing I forgot to mention is subversion of this anti-pattern: technology XYZ is applied in the middle of the project or in the finalizing phase.

Comments have been disabled for this content.