Conway presents an interesting frame for thinking about the act of application building.
However, I think I view the application building aim through a more complex lens. In building a great application, one is building a dialog with the end user. That dialog will consist of a complex interaction of pictures, motion, text, sound, and timing. Some parts of applications are more appropriately oriented around text, and some more around pictures. This leads me to conclude that the best applications must be (a) written by teams, (b) written by people familiar with thinking about which kinds of communication are appropriate, and when. These cannot then be six-year-olds, or even sixth graders, but possibly require people with college level skills, or beyond.
So why not target the opposite extreme - what can make those experts able to move more quickly? How can they improve their code in front of the customer, on the fly? How can we make them more efficient? (Perhaps very useful questions for the golang-nuts mailing list). Then, once we start hitting upon best practices there, then we can start pushing those skills back to elementary school!
Just like how we teach elementary school children how to write, not because we expect them to be great writers, but because we believe that teaching individual skills is the right approach to teaching overall writing well. Same pattern already applies for programming. Let's teach formal logic, let's teach writing down task instructions, let's teach abstract thinking. Even in a world where we can completely redesign how we build applications, we'll still need those things.
Eric.