As the founders of Google will tell you, to know CS, it is obviously not necessary to "sacrifice business". Fair, but I was trying to express that in the conte

As the founders of Google will tell you, to know CS, it is obviously not necessary to "sacrifice business". Fair, but I was trying to express that in the context of my career. I'm not going to be creating the next Google. If you're only reaching for a 9-5 job, as most outside of the HN crowd are, it is a sacrifice - at least from my point of view. My argument is that this is short-sighted. I really don't think it is true. Once you start in Rails, your thirst is going to become strong to learn everything else there is to possibly know about CS. I guess if you actually do stop at Rails, sure, but that indicates a lack of interest in the study, which means the chances of success in a CS program are low to begin with. With that said, I've been in the industry for about 15 years now and I haven't really seen any change. The languages and frameworks may have, but the stuff most people are being hired for are, in concept, the same as it has always been. That is probably not going to change in the next 15, unless some radical technologies are discovered.