A post was made of: “Using the same tools.. a dev shouldn’t be building a system using xyz tools and another dev building with abc tools. Reduce the amount of redundant tools”
The problem is that someone up top needs to show growth and innovation, a year end bullet point is needed. Some vendor takes them to lunch and shows them a pamphlet of their product. The next thing you know a “high valued important product has been purchased for the company to do ”, but wait it gets better.
They then goal, or force, MD’s an their reports to use new and improved said tool. After a few months of this enforcement, it’s hailed as a gleaming success. It doesn’t matter if there’s other tools being used already that does the same thing…this is new, but wait it gets better.
Often times, its realized that either:
a.) the new tool does not scale up
b.) the new tool is too expensive on the licensing renewals.
c.) the new tool does exactly what the read pamphlet says, to a point. Yes, it inventories all your servers……but not vm’s for example, you shoulda read the fine print. Remember that old chestnut.
Over time the newly purchased tool is either partially used and\or is forgotten about.
Lesson learned? NOPE! Rinse, repeat. So long as these up top decision makers, these stellar shot callers keep thinking like this and fall for the over the top sales pitch, it’ll never change. All that you need to do is take Bob out to lunch at a fancy restaurant, tell him he’s awesome to boost his ego and the sale of the new tool to Citi is as good as done.
It’s all ok though, we can just lay more people off to pay for it, right?