3 ms·
You can do some of the following: - If there are no code reviews, ask developers you look up to to review your code. Review or be a silent participant in others
by rmk 6y ago
You can do some of the following:
- If there are no code reviews, ask developers you look up to to review your code. Review or be a silent participant in others' code reviews as well.
- Ask senior devs to give you a tour of the entire system. Ask for code walkthroughs of parts that you will not be working on also.
- Participate in design reviews, providing thoughtful comments.
- Ask plenty of questions, including on seemingly obvious things so that you catch up to the others on the team in terms of your understanding of why things are the way they are.
- Whenever you first open a source file, take a few moments to browse through its version control history.
- Familiarise yourself with the build, CI/testing etc. loop of your product.
- Read the Unit Tests for parts of the system that you do not understand at first. They are usually an excellent starting point to get an understanding of the system.
- If there is a separate QA staff, make time to talk to them and ask them to show you how they put the system through its paces.
- Ask your manager to give you concrete goals for your first three months, and also to give you a few stretch goals. Try your best to exceed your goals, including your stretch goals.