After reading Jeff's post plus the comments here, it seems we in the programming industry can certainly agree on: lots of assumptions. Assumptions about how mu

After reading Jeff's post plus the comments here, it seems we in the programming industry can certainly agree on: lots of assumptions. Assumptions about how much value is involved for a programming neophyte. Assumptions about what one would do with a little knowledge. Assumptions about how valuable the study of programming is for an individual. Assumptions about what one can be empowered to do, once gaining a little knowledge. I'm sure there are more. Our assumptions may not be equal, but we sure have no problem making them. No matter if you support Jeff or feel he's way off base, there's a lot of judgment involved this topic, and we should really just stop for a second. As professional developers/programmers/architects/etc., it's easy for us to have opinions on this subject and find any scenario to support any argument one way or the other. The exercise of positing an argument, one way or the other, is actually unnecessary. For us to judge if something has value to someone else, a little or a lot, makes assumptions about how someone will discover, learn, expand, grow. In spite of our experience in the field, making such broad assumptions might be accurate in some cases, but the variability of outcomes shouldn't be underestimated. Should we encourage everyone to learn? Maybe, but I don't assume it's the best use of time for everyone. Should we encourage everyone to go deep, perhaps enter the profession? I'm not sure of that, either. But I do know that answering those questions with broad absolutes as outcomes requires quite a bit of hubris on my part.