Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Looking for VB ansers 2

Status
Not open for further replies.
IMO, this is probably the most important point made:

"Study other people's code. Don't just download the code and plug it into your projects. Take it apart; study it; learn how it works."

Also adding: "Study other people's code...and test it thoroughly!!"

We all make mistakes! And I make many.
Often undeliberate (get distracted; read too fast; type too fast; was thinking of something else; ran out of coffee; the good looking over there; etc.), and the code is then faulty.
And, one other reason: There are soooo many different situations and factors to consider, that we are bound to forget something. Someone else testing, sooner or later, will find that/those mistake(s) though...The more "eyes", and/or more experience there is, the better it gets.
 


Learn from the mistakes of others.
You don't have time to make them all yourself.

(I forget who said.)

Cassie
;-)
 
CCLINT is absolutly right. Great point, you get a star.

If you download code take the time to learn it inside and out. It will save time in debugging because you will understand how it is working and how to resolve the issue. Nothing worse than not understanding how or why an error occurs.



Thanks and Good Luck!

zemp
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top