This reminds me of Perl's motto: There Is More Than One Way To Do It. Regardless of the community, we generally all strive for the most efficient way to accom

This reminds me of Perl's motto: There Is More Than One Way To Do It. Regardless of the community, we generally all strive for the most efficient way to accomplish a goal, but the definition of "efficient" can vary: execution performance, elegance, ease of developing, ease of integrating into X... Often, one or a few leading solutions emerge but it's tempting to take those pragmatic optimums and turn them into law—or worse: follow them for the wrong reasons. It's a good idea to know why you're using a particular design tradeoff, and remain flexible to change if you find your constraints have changed. Some environments make this interchangeability easier than others but there's almost always a choice.