Which way is better

I was always wondering which is the best way to program for a functionality on a given language.If look at a code written two years back and if i reorient it in a better way is it evoltion or a bad program then. I can tell myself that i keep evolving everyday.

I keep thinking and acting for what will make my evolution better or what will suffice my thrist to write the best code? Can I achieve the best expression only when i know the different expressions... So where can I find the different expressions? So similar thoughts are there for any person who likes to write a good program...

So, talking about different paradigms or expressions. I found this article
Lisp is a sin from Sriram and the above atricle from Don Brox quite interesting...

Case Study --- Simplistic approach to Web enable a COM Application

A typical distributed Com app. architecture could be
Com Client --> Complus --> database

Difficulties could be
1) Methodology to be adopted.
2) Serializing the various com objects and data types like
i) Recordsets
ii) Safearray
iii)Strings
iv) Variants

The most promising methodology could be using .net webservice layer between the com server and the com client. Another layer of .NET can be introduced between the com client and the new webservice layer. This will minimize the client code changes whenever there is a chage in the protocol for communication between the client and the server.
Also explicit conversions of COM data to a serializable format can be done in this layer.

Eventually the new architecture will look like...
Com Client -->Complus mirror -->Webservice--> Complus --> database

Serializing Recordsets are something to talk about:
The different methodologies could be...
i) Persisting recordsets as xml in a Msxml dom objects, which can be serialized when represented as xmlnodes.
iii) Converting recordsets to datasets for serializing and then reconstructing the recordset thru xslt transformation.