28
JS96
6y

The senior programmer at work commits so rarely that in 3 months I committed more than him in 3 years (e.g. 0 times in September)...

What’s the point of having a repo on bitbucket if most of the time the latest code version is only on his machine?
And why I have to recreate and repopulate the db every fucking time because he made so many changes to the structure, which of course conflicts with mine?

Comments
  • 5
    Have a sit down with him.
  • 6
    He doesn't understand version control. He needs to have training so he does, otherwise it's going to cause massive problems down the line (if it hasn't already.)
  • 5
    Sounds like old CVS/SVN habits.

    "Don't commit as long as you might be the build breaker!"

    Those monster commits are always toxic.
  • 2
    @Yamakuzure Even with SVN though, that's a hell of a time to wait.
  • 1
    Yeah let me guess. He's just before retirement and also doesn't like issue tracking.
    Sounds like my own colleague.

    Show him branches.
Add Comment