3 ms·
> If you use any others and you are a normal developer, chances are you are overcomplicating things and should rethink your way of using git. I strongly disag
by Shacklz 4y ago
> If you use any others and you are a normal developer, chances are you are overcomplicating things and should rethink your way of using git.
I strongly disagree with this one.
Git is one of those constants in our developer-live that is bound to stay for a long time. Probably longer than most other tech/tool that most of us use and learn on a daily basis.
The fundamentals of git aren't that complicated, the datamodel isn't any more complex than what you get taught in an introductory datastructure course. And once you understood it, you can leverage it to create an actually readable and usable commit history instead of the unreadable mess that your average enterprise project is. In my opinion, it's well-worth the trouble of taking an afternoon to understand git beyond the commands you've mentioned.
- kramerger 4y ago> The fundamentals of git aren't that complicated, Agreed > the datamodel isn't any more complex than what you get taught in an introductory datastructure course. Also true. The problem is that people love to shoot themselves in the foot by overcomplicating normal use of git That's all fine, until you try to push to someone else's repo and things start to crack. So as a person who had to maintain a fairly large project, and had to fix a lot of madness from developers I nowadays suggest everyone keep their git adventures to a minimum.