Software Engineering at Google (2017)

Re:Software Engineering at Google (2017) by StreamBright on Friday January 04, 2019 @06:42AM (#18823328)

Even git or hg branches are horrible. Once you have multiple people working on the same codebase and touching the same files it is pretty horrid to manage. I know several companies not using branches because the merge conflict resolution takes too much time.

The PDF explicitly calls out the time consuming part:

"Almost all development occurs at the “head” of the repository, not on branches. This helps identify integration problems early and minimizes the amount of merging work needed. It also makes it much easier and faster to push out security fixes."

[ Parent | on HN ]

Re:Software Engineering at Google (2017) by sigsergv on Friday January 04, 2019 @09:05AM (#18824087)

Rebased branches in git are nice (for one developer only unfortunately), there are some pain of course but when rebase is performed often (once a day) it consumes not so much of time. The real pain begins when some huge commit is pushed to HEAD but it still manageable.

Anyway, I feel sad that so much efforts were put on really nice VCS concepts and almost no one use them in enterprise development.

[ Parent | on HN ]