Merge then review
Merge then review
![](https://programming.dev/pictrs/image/f66b1ebf-2e3a-4ef6-8721-53c815c53819.png?format=webp&thumbnail=128)
![](https://programming.dev/pictrs/image/f66b1ebf-2e3a-4ef6-8721-53c815c53819.png?format=webp)
Move fast and break things.
Merge vulnerabilities.
Double the work.
Merge code without tests.
Anything, but don't let code become stale.
You're viewing a single thread.
All Comments
132 comments
I just commit directly to master with auto-deploy like a real cowboy, yee-haw!
44 0 ReplyWhy review at all when the users will do this for you? Merge, deploy and move on. If it's broken they'll tell you.
I'm definitely going to start doing this at work. We don't want our embedded firmware for medical devices to get stale.
7 0 ReplyRight? Who needs a QA team when you can use real live customers for testing
3 0 ReplyIt's the Microsoft way.
2 1 Reply
132 comments
Scroll to top