in reply to
IYHO, what do you consider good code?
I have two things to add to the tremendous advice give by the other monks. Remember to test, test, test, before something goes into production. Also, look back at old code when you have a quiet moment, this will allow you to see how much you've learned, and if you improve it, esp. if boss wasn't expecting it, will usually impresses people. This may not be coding style, but debugging and maintaining
style, which I think is important as well.
Update: Added last sentence
"Pain is weakness leaving the body, I find myself in pain everyday" -me