Time for the morning ramble -

First off I am old-school. What I do is a reflection on me. It is not the specifications not the tool. Further it is not a product of them or those in accounting or Human resources, it is my product.

Second when it fails I do not point fingers at the OS or other new code nor the database. I own the problem. I find the problem and I either have one of the other staff address the problem or I fix it myself. And when the OS or other technology changes, my work needs to either have anticipated the change, be impervious to the change, or be changed to work on the new platform.

Third I remember the old TV add where a automobile break repair company said that they stand behind their product. They were openly criticized because if they really believed in what they were doing, they would stand in front of their product, and later they did as cars would drive right up to them and show that the breaks really worked. I need to stand in front of and behind my product. It is not my output but part of me. I created it and no one else can understand it without my insight. I need to make it work right.

Lastly - I believe that if I can trumpet my successes, I should also admit my failures. Not everything I have done has worked first time every time. And some things has had to be readdressed and redone. SO WHAT! Development is a series of controlled failures breaking potentially new ground on the way to a previously unachieved goal. By definition failure is part of the process of getting there. However, once you have achieved the goal, you should be able to develop a process that gets you there repeatedly without failure.

Parting word - When perfection is expected, the one who is expecting it of others is most often disappointed. When it is expected that one must work with a creator to achieve a level of success over time, the goals are often reached.

M.