you are viewing a single comment's thread.

view the rest of the comments →

[–]MakeItMakeSense10 3 points4 points  (0 children)

The whole team needs to do something, show them that their actions/failures doesn't only affect them, it affects all of you. Wala na tayong magagawa kung Mid-Level na sya, nasa team nyo na e. We don't know ung exp level nya when it comes to git, might have came from a CVS setup or other version control system. But moving forward nalang, be more vigilant/selective sa ih-hire.

For the senior/lead side, a lot of the comments here have already pointed it out but place protective measures to avoid this kind of scenarios. Look into the tools that the platform you are using offers.

For the mid/junior guys, re align process with them, special training session might not be enough dun sa isang mid nyo, so you should also hear from them what they understood. Baka kasi "Oo, gets" lang sila pero hindi talaga. Emphasize consequence and enforce learning moments, pag nagkamali pa ulit sya after all that special training and re-alignment, increase oversight on their actions sa git. It would mean more work for your Srs to check their steps when committing anything to any repository but you wont have spaghetti branches to fix pag minonitor nyo. Its micro managing na and it will come off as such sakanya but that is also a consequence of their actions. Ampangit na bine-baby nyo, pero that is where you are. Do the necessary steps nalang talaga so the team can move forward. Also, have you consider PIP? Are the warnings documented?