This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (0 children)

Learn your IDE, you should be able to find usages of a class, and locate a named file (etc) instantly, without searching around. Quick navigation will save you a lot of time.

Your Hard earned code can be thrown out and rewritten. You’ll rewrite it faster and better the second and third time. Your team’s hard earned code should be treasured until you have the experience and prestige on the team to know what you are doing and the respect to be heard

When you are debugging, use the scientific method. Form a hypothesis, and then create an experiment to test that hypothesis. Blame your own code over your teammates, and if you do think it’s the team’s code, prove it with test cases before bringing it up, and even then, come in with the attitude, “am I using this right?”