> Downside to this approach is that you need a starting point like "should I be a Python dev or Ruby dev" which mostly is asked by new fresh starters - and my a

> Downside to this approach is that you need a starting point like "should I be a Python dev or Ruby dev" which mostly is asked by new fresh starters - and my answer is pick one, if it sticks and is your 80% (even if it is not really) continue if not go for another one. I remembering hearing in a podcast something like "If there's a fork in the road, pick it and stick with it. You'll end up in a better place two years later than if you just spend two years weighing the options. And if you stick with something for a period of time, it's usually easier to switch to something else than if you didn't do anything."