I fear the point is still missed. He used the analogy of the auto mechanic, which I liked very much: "Isn't knowing how to change a tire, and when to take your car in for an oil change, sufficient?" Exactly.

Learning to code is like learning the basics of auto mechanics. If you own a car, it would be very beneficial to learn the basics of how a car works so you know to change the fluid levels, why they are important, and all 101 level maintenance. In a similar fashion, learning to code is like learning the high level basics of how computers work. We don't expect an business guy to learn to develop kernel level drivers, antialiasing algorithms, or detail on public-private encryption just like we don't expect every car owner to know how to repair a broken starter motor or diagnose a vacuum leak.

For a business guy, truly learning things like the detail required, difficulties in collaborating on code, and how larger programs take more time to change are all vital pieces to understanding their business.