3 ms·

I disagree. I am glad I took some spare time to learn RoR coming from a .NET background. I had no problems to solve in RoR that I couldn't solve in .NET. I ju

I disagree. I am glad I took some spare time to learn RoR coming from a .NET background. I had no problems to solve in RoR that I couldn't solve in .NET. I just explored it and learned about different ways of doing things. I am sure it has made my .NET programming better too. Also learning some RoR has got me also using Linux and Git. I learned a bit about Nginx etc. I went to some interesting RoR meetups. I gained a lot from it. So I encourage programmers to learn other languages and techniques, for the sake of it! -- 10. Learn another programming language / framework tool 20. Have fun with it 30. Realize you can now solve problems you previously couldn't 40. Profit

SixSigma 12y ago
There is some confusion, you are agreeing with me. I mean don't try solving novel problems in your day job with novel tools and techniques. Use known tools to solve problems. Lean new tools when not solving problems.
- bbcbasic 12y ago
  OK i misunderstood you, but I don't see how you can avoid learning new tools when solving problems. You must often hit the point where you think "surely there is a better way to do this, lets research it" - then find new tools, spike them and then use them? No? However what I think you are getting at maybe is people who think stuff like "Node.js - that sounds funky, oh.. Hadoop - thats hip at the moment how can we use that?" perhaps for fun, or to enhance their CV. That is dangerous. You end up with completely the wrong tool for the job!
  - SixSigma 12y ago
    Yes, that's what I mean. Software is all about building tools. I mean like "I know, I'll do this client job in Lisp, I've never tried that" which is probably a bit of an extreme example but I have learned similar by experience :)