Merge then review

agilob@programming.dev to Programmer Humor@programming.dev – 721 points –

Move fast and break things.
Merge vulnerabilities.
Double the work.
Merge code without tests.
Anything, but don't let code become stale.

143

You are viewing a single comment

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.