It's an axiom that you should "commit early, commit often." Likewise your local drive should not be the only place clyour work exists. That means it may be incomplete, broken, even ill-considered. On any reasonably sized team keeping everyone aware and up to speed with what everyone else is doing is very difficult. That means someone might see work that isn't ready and make the logical assumption that it is. Or this code makes difficult to reverse changes that now have to be backed-out on everyone else's environment when it changes. I can only imagine the hell of trying to make my work mesh with someone else's only to have theirs change completely the next day. At least if that only happens once I skip all of the intermediate steps. I don't need to see everyone else's sausage.
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.
It's an axiom that you should "commit early, commit often." Likewise your local drive should not be the only place clyour work exists. That means it may be incomplete, broken, even ill-considered. On any reasonably sized team keeping everyone aware and up to speed with what everyone else is doing is very difficult. That means someone might see work that isn't ready and make the logical assumption that it is. Or this code makes difficult to reverse changes that now have to be backed-out on everyone else's environment when it changes. I can only imagine the hell of trying to make my work mesh with someone else's only to have theirs change completely the next day. At least if that only happens once I skip all of the intermediate steps. I don't need to see everyone else's sausage.