Maybe I'm that ahead of the curve, but I understood inmediately what an algorithm that "takes a Bernoulli sequence with p != 1/2 and outputs another B. seq. with p = 1/2" is. Or perhaps the author chose a wrong example.
If anything, it shows that this field is mature, and has progressed to a more general vocabulary. It's still light years behind other kinds of engineering, IMO.
I think part of the problem is that if you know what a Bernoulli sequence is, there's no need to read that. It's a useful abstraction for building things at the next level, but not for teaching things AT that level.
(I have a EE degree and disagree that CS is particularly far behind it; it's not like they're solving problems in hardware that are just way beyond our ability do in software are they?)
It's not at all accessible to children, at least compared to what it could be. I've been writing code for money for 20 years and it took me a long time to understand that paragraph. It is concise, but it's not clear. And worse there is no indication of just how important this clever little algorithm is.
The point is this, even if I'm the fastest coder on earth, write the most elegant software, quickly with very low bug rate, innovate and spread my creativity to the team, if I don't know things like the above, I probably won't be able to work for Google... or will ever be considered a "real" software engineer. Computer Science and Application Development overlap, but are not the same thing, and require at many times, different skills. A great front end developer can understand performance and write efficient code, regardless if he knows all the details of big O notation.
If anything, it shows that this field is mature, and has progressed to a more general vocabulary. It's still light years behind other kinds of engineering, IMO.