I had commented in another blog (thomasgardnerofsalem) that deals, in part, with technical issues. There, I mentioned that I had female cohorts all along the way. Some of whom were better than their male peers, in my mind.
The post here is motivated by seeing the post at the Computer Science Teacher site. It will be interesting, as Alfred wrote, to watch this unfold. If thrusts, such as this, can get people interested in computing, that will be a great step forward.
At one time, computer science was generally interesting to the younger folks. Let's say, a couple of decades ago.
Then, finance came to fore (to my puzzlement, at the time). That is, this was true until that last crash (do you remember?) brought reality back to everyone's mind. As things crashed and the dust settled (is still doing so), we all had a chance to look more closely at what went down. For instance, consider the pay differential that we saw between finance and, what might be considered, more critical work.
Aside: Did we really learn from the machinations of those times? The computer proved to be problematic (one of a very huge set of examples) and will continue to be so. For example, the issues raised by Minsky are multiplied when computers are involved.
One thing that turned people off about computing was the tedium which may have been a reaction to the difficulties and complications that one can face. Too, large systems can be very hard to do and to keep running; but, tools have always been the clever adaptation to handling such requirements. There were other things that caused negative reactions.
Aside: A world of a zillion little apps is not any major improvement. Those issues that faced us before are still around.
Yes, code is (can be) fun especially if you're in the driver's seat (yeah, Zuck). If the requirements are being imposed upon you by others, then it's really a process oriented affair that has a much different flavor. This goes beyond the bazaar/cathedral discussions. What? Yes, discussions about truth are pending.
Blockly seems interesting. Perhaps, it can lift the discussion, at some point, beyond code (as in, coding at what level?) to where we can start to "truth engineer" as needed and to get peoples' rights, in so far as they deal with computing, to the fore (we're coming up on the 800th of the (first) Magna Charta signing).
Aside: In a sense, everyone ought to code. And, there are many layers of code. Those who deep dive (yeah, wizards, I mean you of the power) have no greater claim to the truth of the computational experience. On the other hand, many of the upper echelons would not dirty their hands (ah, how do we get them out of their sheltered world?) thereby showing their lack of respect for truth (ah, this can be demonstrated).
Remarks: Modified: 06/22/2014
06/22/2014 -- I would be impressed if I heard that Sheryl would deign (or stoop) to coding. Without a code sense, how does one handle truth (yes, mathematicians, you, too)?