The right tool for the job

A general problem developers have is they become slaves of the tools they use. Read on the net and you'll see thousands of people defending Lisp, Ruby, Python, Java, ... - claiming their programming language is GOD's gift to developers. The same can be said about editors (for example Church of Emacs), operative systems or anything in between.

A major problem with this kind of thinking is that it blurs the judgment. If you think Ruby on Rails/Lisp/Emacs/VIM is the best for all jobs, then it's really hard to evaluate anything else - - and you may end up doing some very bad calls.

The solution

• be more open-minded
• don't be fanatical
• don't attach emotions to the tools you use
• don't be a slave of your own patterns

A real master sees a tool as a tool, not as a religion or something a master is emotionally attached to.