732
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.
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.