note cLive ;-) <p>I've evolved a few simple rules: <ul> <li>[id://170920|welcome mistakes] and don't try to pretend they didn't happen - you learn more that way, and leave the bad thought process open to others to see the assumptions you made :)</li> <li>always be paranoid that there's a better/more secure/more efficient way of doing something</li> <li>accept that this is not the end of the world if you can still get the job done (you can always apply new stuff learned at a later date)</li> </ul> <p>My general philosophy of coding is that you're doing well as a programmer if you know what question to ask. By understanding the question, you can work out the answer. It's when you don't know the question that things go wrong. <p>Basically, [BrowserUK], I think you're suffering from programmers' paranoia. It's perfectly normal and I'm sure you'll feel better in the morning :) <p>.02 <p>cLive ;-) 275994 275994