This is an excellent article, but it's almost advocating a doctrine, when perhaps the best approach is to have no doctrine at all. I appreciate the idea of mas

This is an excellent article, but it's almost advocating a doctrine, when perhaps the best approach is to have no doctrine at all. I appreciate the idea of mastering a language or technology. It is often much easier than adopting something new. But the main reason for adopting something new, is to make doing something much easier. That 'something' is often a call to solve a new problem. I feel you generally come to understand why you should adopt a technology, after mastering your current set of tools. If we were to really take to this idea of maximising the tools that are already available, then we probably all still deploy applications over FTP. I think the two most valuable take-aways for me, are the importance of discussion, and the desire to have as small a number of dependencies as possible.