&#x27;Place I think it to be&#x27; is completely orthogonal to beautiful code. :P<p>From my own experience, many, many times, definitely a majority of them, when I have had performance issues, and finally found the bottleneck, and fixed it, my code was more beautiful afterwards. Algorithms were simplified, duplicated effort was removed, etc. One major one in my mind was where code was attempted to be reused, but in doing so it caused an O(n^2) behavior, where an O(n) could have been done instead. Upon finding it, and refactoring it, the code had fewer interdependencies, the logic was far more straightforward, both things I find to make for &#x27;beautiful&#x27; code, and it ran far, far faster (from &#x27;this particular operation takes an hour&#x27; to &#x27;this particular operation takes &lt; 1 second&#x27;). Had I invested time up front after making it work to clean up the code (rather than stop at &#x27;it works, good enough&#x27;) I would have stumbled upon the same fix, even before seeing the performance issue.