Software Engineer at InVision. Full-Stack JavaScript dev, with passion for front-end development.
Psytrance DJ on weekends, playing in local clubs (yeah, that means: Goa Parties!) :D
Great article! I really enjoyed reading it. 😃
Another important point is, that you communicate any action with the team before making changes that might impact other people's work. Especially when in this area of the code is being worked on. It turned out to be a good practice to talk with the ones working in the area and mutually agree with them on a certain way of to implement the feature/fix the defect. Gently remind them when they don't stick to the agreement. If this won't change anything, you can take action and change the code with the agreement of management on your own.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great article! I really enjoyed reading it. 😃
Another important point is, that you communicate any action with the team before making changes that might impact other people's work. Especially when in this area of the code is being worked on. It turned out to be a good practice to talk with the ones working in the area and mutually agree with them on a certain way of to implement the feature/fix the defect. Gently remind them when they don't stick to the agreement. If this won't change anything, you can take action and change the code with the agreement of management on your own.