You are right, Sascha. Many of these problems happen even the dev are working face to face with the team. I don't know how many times someone goes out to lunch and forgets to commit some important code. :-\
Yes for sure, the lunchtime commit is very important I think. But the most developers are scared about the "Do not commit stuff that is not working" so they don't do it. I think that it is OK when someone commit not fully working stuff, but he must inform the coworkers about, or do a push in a separate branch. :)
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.
This article explain not only the remote work. I think this will be the same for all workers, it dies not matter if he is a onsite or offsite worker.
You are right, Sascha. Many of these problems happen even the dev are working face to face with the team. I don't know how many times someone goes out to lunch and forgets to commit some important code. :-\
Yes for sure, the lunchtime commit is very important I think. But the most developers are scared about the "Do not commit stuff that is not working" so they don't do it. I think that it is OK when someone commit not fully working stuff, but he must inform the coworkers about, or do a push in a separate branch. :)