5 ms·
My company is currently transitioning from a 20+ year old Perforce depot to a git workflow. We're certainly having issues like you describe, where people don't
by cdcarter 4y ago
My company is currently transitioning from a 20+ year old Perforce depot to a git workflow. We're certainly having issues like you describe, where people don't know (and don't care to learn) the mechanics of git. And I agree, git is the kind of tool where once you understand the primitives, you can quickly start making lateral leaps to solve problems.
But I do think that there's room for a better mechanism for orchestrating "macros" or building other workflows on top of git. I know a lot of developers who'd love the ability to pretend they're using p4.
- lumb63 4y agoMy company wanted to "script away" all the "pain" of using Git to make it equivalent to Clearcase. I think it's a smell. If you want to use Clearcase, use Clearcase. etc.
- ziml77 4y agoI don't think that's necessarily a bad thing. Using scripts to change how devs interact with git is just putting a new porcelain on the plumbing.
- gdprrrr 4y agoExcept you now have a set of tools without proper documentation and no way of googlng issues. And chances are you created a new leaky abstraction.