I don't agree with Master Foo's responses, really. The thing about HR is that they're always telling you, "If you have a problem with X, come to us." Meanwhile they are beholden to the company. If you bring any complaints about the workplace to them, the main thing that happens is it goes in to your file.

HR is useful if you're running a company. They can take care of some tedious stuff and help you cover your ass legally. And it might be worthwhile for a Joe Developer to go to them if you're party to a debacle like this.

But otherwise avoid them.

http://paulgraham.com/notnot.html

Almost all the other essays at his site are worthwhile if you are considering a startup.

Some of them will go to sales or marketing, or become recruiters. Then when they talk with their customers, they'll tell them, "Yeah, I was once an engineer, just like you! Then laughs self-deprecatingly I went over to the dark side."

These aren't part of a overarching philosophy, but they come easily to mind:

1. Learn vi or Emacs. Actually, learn a little vi no matter what, because it's the only decent editor you're guaranteed to have on non-Windows machines.

2. Ask dumb questions.

3. If you're stuck working on stuff you're not crazy about, spend a few evenings working on something cool that is useful to the company. Most shops will give you a shot at building it out.

4. Get good at estimating, communicating, and sourcing IP and tools.

5. Work at a startup (or start one!) before having kids or developing other attachments makes your risk tolerance too high. Paul Graham is right about the experience multiplier you get at a startup.

6. HR is not your friend.

7. Profile your code. So much learnings.

How are they going to further discourage the use of Emacs keybindings?