IBM....
I've interviewed a guy from IBM before. He insisted on commenting everything and having getters and setters for all of his fields.
If you google you can find out why I didn't think this was such a good idea...
https://www.google.co.uk/search?sugexp=chrome,mod=11&sou...
Being in a company has a lot to do with how well you get along with people. You're new, and so I suggest that you listen carefully, ask questions about things that you don't understand (otherwise you'll feel like a dumbass next time they bring it up, and you still don't know what they're talking about).
When you've been working somewhere for a while you also tend to dismiss the problems around you. Make sure you note down all of the things that you find wrong about the place - ask people why these things are they way that they are - it could be a misunderstanding on your part, but it could also be that there are genuinely things that need fixing.
Make sure you keep a notepad on you - note down everything that you learn, problems that you see etc - it'll come in handy.
After a couple of weeks you can start acting on fixing the problems that you've seen - if you actively seek to solve problems, then you can become a hero in the company - the guy that made our lives better.
Lastly remember that if you want something you'll have to fight for it. Don't be afraid to disagree with people, but you have to play a fine game when you've just come into the company - you don't want to piss people off, but you also don't want to set the expectation that you're OK with shitty code.
I hope that helps! have fun out there ;)
Lou
http://TheStartupSlayer.com