>erst>>>Sometimes I wish a programmer had just written comments on what he/she was trying to do and let me write the code! It would be simpler than debugging.
>>>
>>>Unless you are following a programmer that had no idea of what the client (user?) wanted.
>>>
>>>Hardly any success stories come from projects that failed to recognize the requirement.
>>
>>My problem is more the talented but uninterested developer <g>.
>>
>>But, as you say, design bugs are the most serious and expensive to remedy and in most cases its best to start over. That's the story with so many Access applications. "We had Joe work on this in the evenings and weekends. It's 90% done, but unfortunately, there's duplicate data and we get more and more errors." The biggest problem is the client's understanding that there's only 10% left to go.
>>
>I would bet that many of us - especially when thrusting through the last 10% of the project, fall into the "talented but uninterested" category. Thats when professionalism (needs to) suplant our (deminishing) code-warrior-force<s>.
>
>It seems (during those last phases), there are plenty of reasons to ignore the keyboard and "really think something through". Those 3 or 4 lines of click event methods really need to be thought out - or the callouses on the heel of our hands need a break, or wouldn't some top ramen be nice now - the list is endless. Bernston will probably start a thread on "favorite excuses" in the near future<g>.

Everyday one faces the decision of doing 3 things well or 10 things poorly. The big difference for me is that if I do 3 things well, I can say that they are done and move on to 3 new things. If I do 10 things poorly, it just seems that I keep doing them over, and over and over again and never quite complete them. Deva vu all over again!


>
>May the force be with us!

AMEN!