"When all you have is a hammer, everything looks like a nail" Don't go into the trap of rewriting the code the first week, all new coders think that is the onl

"When all you have is a hammer, everything looks like a nail" Don't go into the trap of rewriting the code the first week, all new coders think that is the only solution on the first job. It takes time to realize why the code ended up in that state in the first place and badmouthing previous developers doesn't make you look very good. Management might very well know why the codebase looks like it does, priority is often time, not quality. Something that looks like a bug might have become a feature that the users depend on. If you remove that bug you have created another instead risking corrupting data and/or angry customers not able to do things the way they are used to. For all you know you are being tested for work culture and how you behave towards your collegues :-)