Breadth and depth are both very important. Too much breadth and you have a hard time getting any non-trivial job done. Not enough breadth and you use the wrong

Breadth and depth are both very important. Too much breadth and you have a hard time getting any non-trivial job done. Not enough breadth and you use the wrong tool for the job. If you want to be the best dev possible, it's probably good to keep up with the latest in terms of adding those alternative solutions into your own conceptual framework, but it's distracting to spend too much time with them unless they truly are the best tool for the job at hand (and marginally so in terms of time invested). I suppose it's like reading non-fiction books. As soon as you believe you understand the author's perspective in sufficient detail, it's often best to set the book aside and move on to the next one. You are under no obligation to read every page.