Howto code emotively

Let's assume Pirsig's assertions that quality is undefinable and that it sits as a parent to both qualititive and quantitive activities (romantic and classical, respectively). It's interesting that the lexicon is not quite good enough to have quality separate from the romantic side in this case, when quality has to be linked completely to both, if the assertion holds - but I digress.

Therefore, if the objective of any activity is to achieve a high quality result, one has to *do* both the analytical side and the emotional side.

This is a weird proposition for/from a positively analytical being such as myself. How can one apply one's emotions against a piece of computer code?

The answer is one that is based in the assertions of the eldar codemonkies of yesteryear (or at least the good ones). Programming is art. So much of it is to do with feel. One could, given sufficient time and motivation, abstract into infinitum. It's simple to add more and more flexibility to any piece of code. Performance (speed/size) can almost always be improved. But at some point, the sage will say, 'stop' (if he's feeling particularly poetic he might add, 'I am at peace and the code is finished, the one necessitates the other').