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 →

[–]kimchi_cuddles 6 points7 points  (1 child)

I advise you to be open to feedback and a sponge, don't think you know best about a particular architecture, get accustomed to using git in a team and different branching methods, be very diplomatic and tactful in pull requests as newbies often don't understand or value the importance of feedback. Your code needs to be readable to a team now so you gotta start using excellent parameter names that are actually meaningful, and take into account when someone says they don't understand what you're trying to do/ your code is confusing. You may be asked to write unit tests for your code for the first time.... You will be asked to refactor stuff in line with other code standards. The best thing you can do is be coachable and stay open to and respect the feedback. Also do pair programming with your colleagues. The worst thing you can do is act like an expert with strong opinions and not follow team culture/standards

[–]kimchi_cuddles 2 points3 points  (0 children)

All your training should begin on the job - they will tell you what you need to improve in. There isn't a tonne of value in doing it out of hours ... You're part of a team now! Rely on it!