Studying the constellations and learning the sky is a great way to get a visceral sense of our place in the universe. When you can't tell one patch of sky from another, the brain doesn't need a fancy model for the reality of it, and you can go around with a kind of subconscious "flat sky" in your head. But when you start to piece the constellations together, and it all connects up around you, that's transformative. Space stops being something that's "up there", and becomes a thing that surrounds you. It's a strange sensation when it first hits you, and well worth the time to achieve it.
Just as it's not immediately obvious when looking at a mile of assembly code what particular algorithm is represented, it's similarly difficult to figure out "what's going on" when presented with a pile of C++
For anything much more complicated than undergraduate level academic exercises, the right design media isn't the code itself, it's the modules and their interfaces and how they are interconnected. This sort of thing is much more effectively captured in diagrams than in linear constructs like code.
To put a finer point on it, the design of any non-trivial system is much more effectively communicated as diagrams. You wouldn't try to convey how such a system works to the new hire, by wading through hex dumps of the executables, or even assembly listings. I've been on projects and had 300K (bytes not sloc!) of C++ source dumped on me, though, and something like that is immune to all but the simplest tweaks until you suffer the pain of distilling a set of accurate diagrams of what's going on.
The banana isn't the art. The art is placing the banana in a gallery and art market context to make a funny and ironic comment about the gallery and art market context.
Programming is a craft. It's not an art, because creating code doesn't comment on, criticise, challenge, distill, or otherwise have anything to do with any human experience outside of programming.