2 ms·
Maybe giving them a git GUI rather than commands to run would be better. You have to merge their work somehow. Limiting the commands they can use would be helpf
by verdverm 4y ago
Maybe giving them a git GUI rather than commands to run would be better. You have to merge their work somehow. Limiting the commands they can use would be helpful. You might consider using Bitbucket, which has much better branch & operation permission capabilities, like being able to block force pushes based on branch naming patterns
tl;Dr this sounds like a people / process issue more than a tooling issue. Try to understand why they feel so rushed that they don't slow down to do it the right way. I suspect certain (anecdotal) cultural traits endemic in hardware companies.
- georgeburdell 4y agoYes I've been evaluating Git GUIs (TortoiseGit being my front runner right now) and I hope that will at least reduce the number of botched conflict resolutions. As much as I want to pin it on these two, this isn't a software group and infra should not get in the way of the job at hand. This is my first time being in a supporting role for the "real workers" in the group and it's been challenging
- verdverm 4y agoYou might think of yourself less as "infra" and more of building the product delivery experience for the team. It's more about servicing the people than wiring together tools, though that is the implementation part. Think about spending more time communicating, introspecting, instructing and proposing. Make their life easier, make their work harder to get wrong. Give them training wheels and tracer bullets over rigid rules and bureaucracy. Be patient with them and yourself