Scott posts his and asks for more, particularly from people like me.  I went to college for history and poli sci and drinking and dropping out...not for comp sci.  I did learn some things about software while in college...just not from college.

The List

1. People talk a better game than they play - don't get too caught up in the latest and greatest, or if you don't speak patterns, or if you never programmed a C64, because at the end of the day everyone does what they need to do to keep getting paid, everyone has written and continues to write hacky code, and everyone could stand to learn a new trick or two.
2. When you catch yourself saying "this will only be a problem if x happens, but the likelyhood of x happening is so low we'll never see it" you're gonna want to go ahead and reevaluate what you just did, and do it better.  I once said that about some number generating scheme that was hacked together.  Day ONE of the system going live there was a collision.
3. The next version of technology x is going to make what you are currently doing easier/faster/more secure/more elegant.  The release after that will do it again, and the effect is multiplicative rather than additive.  See: Generics.  You have a job to do today, so do it with the tools available.  Waiting is folly.

there's a ton more i'm sure, but 3 will suffice for now.