If you’re organisation is small/flexible enough, maybe look into using some kind of stacked diff system. We used graphite at my previous company and it’s amazing for working with these kinds of things where you have a million little things to fix and they’re all kind of dependent on each other.
If you’re organisation is small/flexible enough, maybe look into using some kind of stacked diff system. We used graphite at my previous company and it’s amazing for working with these kinds of things where you have a million little things to fix and they’re all kind of dependent on each other.
I’m slowly pushing my team to git. It’s stupid that we can’t work when the server goes offline
It can be quite overwhelming if nobody knows how to use git.
I know software teams that went back to share code on teams folders after having used git…
Please get a git course for all the developers
I mean, I dabble in got on my own. But I’ve never managed a git for a team.
Thankfully I’ve set up Forgejo to abstract some of the details away.
I desperately want to get my team out of the 80s, but I’m not the manager so sometimes my pushing goes nowhere
Oh I know that feeling. But when you get the hang of it you will never go back