Read Steve McConnell's books
Steve McConnell has written some of the clearest and well documented examples of good software engineering practice.
I do not have any higher recommendations for practicing software engineers, and I am was surprised that these books where not mentioned by anyone here to date. I can recommend Code Complete, Rapid Development: Taming Wild Software Schedules, and the recently released After the Gold Rush : Creating a True Profession of Software Engineering (Best Practices).
In his books, you'll find why working insane hours is stupid and counterproductive (and I used to do it, too. Now I'm way more productive on 40-45 hrs/wk rather than 80-100 and I have a social life), good coding practices - including the relatively unimportant variable, function, and class naming as well as the vastly more important software engineering process itself.
Some people hate process, but I'm afraid that's what modern medium-large software project creation is. You can do it the long & hard way, which is to sit in front of your PC and code. This can be intensely gratifying those of us who like to code for coding's sake. Or you can do it much quicker by using software engineering practices, get a more reliable product and have fewer maintainance nightmares.
Steve's books, and good software eng practices help you get there quicker. If you're thinking of going up the software project management tree, these tomes will save you literally months of development. In addition, get yourself PeopleWare by De Marco and Lister. That's a gem, and you'll have staff who will literally love you when you implement the strategies to get good flow time happening.
Click your way to your favorite online book seller and get them. They are truly excellent references.