729
Merge then review
(programming.dev)
Move fast and break things.
Merge vulnerabilities.
Double the work.
Merge code without tests.
Anything, but don't let code become stale.
Having to go through the process of merging hurts morale and slows performance. Give everyone on your team the right to force push to master.
Yes, especially the newbies who don't know what they're doing.
Keep everyone awake and on their toes.
You're not truly part of the team until you cause a massive outage.
New employees are responsible of at least 75℅ of documentation clarification and process overhaul.
I'm totally on board with process overhaul. Ours was stupid when I started, I said it was stupid, and nothing changed. If someone else comes in and can say it's stupid more convincingly than me, that's great.
Who me? No, must be someone else with my name you're thinking of.
Don't hurt their morale!
I honestly wouldn't see this as a problem. But if you break something it's up to you to fix it. But we also don't do CI. We release features in batches after they have been tested and seen to be working.
I don't know if sarcasm because there are actually maniacs like that in this world
Oops boss just did a
git push --mirror