I get where you're coming from, but I didn't get the impression that GP was ignorant to new developments. In my experience the most important thing is really wr

I get where you're coming from, but I didn't get the impression that GP was ignorant to new developments. In my experience the most important thing is really wrapping your head around a domain to be able to solve concrete problems in it. Whatever framework or programming language you choose to solve those problems with is peripheral, really. Also, most coding is maintenance. So yes, an experienced developer in some language is really worth a lot when you initially start out designing your system. But most of the work spent on that system will be maintaining and extending it and to be able to proficiently do that you need to: 1. Grok the problem domain, so you can connect the real-world / problem you're trying to solve with the code in front of you 2. Have a grasp on the limitations of your own system, which will come with experience as you work longer on it