DEV Community

Discussion on: What conventional wisdom in software is wrong?

Collapse
 
_morgan_adams_ profile image
morgana • Edited

I see this very frequently in common everyday engineering decisions. A recent one I saw was "Which config management tool should we use between Salt, Puppet, and Chef?". Others I see, "which static code analyzer...", "which framework...", "which data store...", "which log aggregation tool...", "which apm...".

There's definitely an element of "avoid the fad" in the conversation, but where I mostly see people get stuck is deciding between the more time-tested and stable options. Each option might be valid, but they get stuck on "find the best".

Thread Thread
 
codemouse92 profile image
Jason C. McDonald

At that point, I like to ask them "Well, which one do(es) you(r team) know best?"

If that fails, and if the basic feature lists of each provides no insight, then flip a coin.

Thread Thread
 
codemouse92 profile image
Jason C. McDonald • Edited

Sorry to reply twice, but I have to wonder...

How many people, by saying "use the best tools for the job", are actually only saying "use my favorite tools for the job"? (After all, "my favorite tools are always the best.")

Thread Thread
 
_morgan_adams_ profile image
morgana

I think this happens a lot and it definitely hurts the conversation.

Thread Thread
 
_morgan_adams_ profile image
morgana

I like your comment about flipping a coin :) It bothers some folks since it doesn't seem like a rigorous argument, but at that point you don't need one.