3 ms·
By "properly" - I mean not messing up your own or others work in unpredictable ways. My dev team uses git properly. They are not some masters in a way that the
by ozim 5y ago
By "properly" - I mean not messing up your own or others work in unpredictable ways.
My dev team uses git properly. They are not some masters in a way that they know each command by heart. They often use visual tools or what is built into IDE. We just have general guidelines and everyone knows how to do basic moves like "get code from remote", "merge others work into your local changes".
We had people who always have problems like "GIT ate my homework", well they don't work with us anymore so maybe it is a selection bias.
But I don't think my team members were NOT studying git for months to get to that level, it just came as they go along. Visual tools help a lot really.
In the end I expect someone with any abstract thinking capabilities to be able to use GIT "properly" after a week of working within the team. Like pull new changes every day, create new branch, create a pull request, merge new changes into your working branch.
- krainboltgreene 5y ago> By "properly" - I mean not messing up your own or others work in unpredictable ways. The parent's point still stands: No one is out there choosing to use git in "unpredictable" ways.
- ozim 5y agoNo, if you have modicum of abstract thinking and spend up to 30 mins daily using GIT you don't use git in "unpredictable ways". If someone is a software developer, for me basic requirement is having possibility to understand this.