Tom,

Again you echo my thoughts exactly. Programming for a living is usually not about "best solution’s" (theory) but about delivering working solutions within the constraints and requirements of the job (practice).

I find that sometimes we do not sufficiently understand the difference between being efficient and being effective. One concerns itself about doing something well while the other concerns itself about doing the right thing.

On the hammer issue- yeah I also have a 10-pound hammer. Its the only hammer I need :) Sort of like my approach to programming :)

Happy anniversary!



>Jos;
>
>I enjoy the term “best solution” as it is so subjective. It means many things to anyone you ask. Some things I take into consideration are:
>
>1. User needs.
>2. Budget
>3. Time line.
>4. Security.
>5. Data integrity.
>6. Communication!
>
>Every client’s requirements are different. I program in a number of different languages and platforms from mainframe to desktop and also take tools into consideration.
>
>There are many ways to be successful in any undertaking and computer programming is no different. Some ways may be “better” than others but if it works and meets client needs then it is “the” solution. Anyone can be a critic and say, “I would have done it differently”, but that is not important to reality. Anything can be done “better”. Reality in this case is what is being used.
>
>Most important to me is to be honest and up front with everyone. I have no need to spread bs to make a positive impression. I do make an effort to find out all I can about a topic before I consider a solution. It is important to think before you act, use your experience and always try to do your best.
>
>By the way your comment about a hammer and nail reminds me that I love to buy and use tools. As an example I have more than a dozen different types of hammers from a delicate jewelers hammer to a 10-pound sledgehammer. I use the latter when all else fails! :)
>
>Tom
>