DEV Community

Discussion on: How should my team use Git for this specific project?

Collapse
 
jessekphillips profile image
Jesse Phillips

I believe utilizing git is the right choice, and will try to argue the system was broken (but may fail not being in the system)

Git's distributed nature provides an architecture with benefits not related to work distribution.

It sounds like these files drive an important function, I would expect issues could come from incorrect edits. Git will provide the simplicity of allowing any member to roll back without knowledge of the edit causing this issue.

On the matter of merging, you'll have issues when there are two edits and those edits are in the same area. If you choose a hard reset then you prevent the tool from helping you keep all changes happening.

If there are patterns to the changes then history provides a list of example edits.

My claim that the old system is broken comes from the idea that mistakes get made and versions history gives insight to those mistakes for the better.

Collapse
 
katiekodes profile image
Katie

Thanks for the insight about the added benefit of easy rollback, as well as the encouragement/rationale for me to learn more about merging!