in reply to
Should I leave behind beautiful code or readable code?
Something about the OP comments (probably the remark about letting "pride prevail") reminded me of one of the earliest PM Meditations that I ever replied to (On Hubris -- my own reply was admittedly somewhat off the mark, but the thread as a whole was delightful). The main point raised there by the venerable belg4mit is quite relevant here, I think.
A programmer (that is, any programmer who derives any amount of personal satisfaction from his or her work) may be naturally inclined to feel that the some piece of code s/he has just written is really good code. But that sense of "what qualifies as really good code" is prone to evolve over time, and stuff you wrote a year (or even a few months) ago may not measure up quite as well when held against your current standards. If viewed again another year from now, well...
And of course, the direction of that evolution is bound to be influenced by your environment. Different (possibly mutually exclusive) things may seem more important (cross-platform robustness, rapid development, modularity, etc) depending on your recent, current and anticipated situations.
Your sense of what is "readable" and what is "beautiful" will change with age. As others have intimated, you may reach that truly enlightened state where "readable" is "beautiful" and vice-versa.
So for now, put aside the more emotional judgments, just do what you think is "right", and hope for the best.