Bjarne Stroustrup, author of The C++ Programming Language

I like my code to be elegant and efficient. The
logic should be straightforward to make it hard
for bugs to hide, the dependencies minimal to
ease maintenance, error handling complete
according to an articulated strategy, and per-
formance close to optimal so as not to tempt
people to make the code messy with unprinci-
pled optimizations. Clean code does one thing
well.

"Clean code" is shit. It doesn't do anything well except read well to humans. Code that runs well by definition needs to deal with error handling and optimizations, not just naive algorithms that assume clean input. Stuff is broken up by stream handling and framework semantics.

If it's architected cleanly, it does all these things while being easily editable, but is no where near just describing one thing straightforwardly.