Is the traditional code review workflow holding you back?
カートのアイテムが多すぎます
カートに追加できませんでした。
ウィッシュリストに追加できませんでした。
ほしい物リストの削除に失敗しました。
ポッドキャストのフォローに失敗しました
ポッドキャストのフォロー解除に失敗しました
Is the traditional code review workflow holding you back?
-
ナレーター：
-
著者：
Have you ever had someone review your pull request, make changes without telling you, and just merge it in?
In the latest episode of the No Compromises podcast, we discuss whether the traditional code review workflow still makes sense in a world where AI tooling lets developers move faster than ever.
Aaron shares two real situations where a reviewer fixed and merged code without discussion, and we dig into why the lack of communication is the real problem, not the act of fixing things itself.
We also get into commit strategies, how friction in reviewing someone else's changes kills the learning, and why well-worn workflows deserve a fresh look when the tools around them have changed.
- (00:00) - When a reviewer merges your PR without asking
- (03:31) - How we handled it differently with time pressure
- (05:43) - Should the reviewer just fix it and merge?
- (08:02) - Too many commits create friction for the author
- (13:44) - Silly bit
Get the kind of dev insights that make you rethink everything, delivered to your inbox via the Mastering Laravel newsletter.
Your team is not the only one figuring this out. Join the conversation in the No Compromises community.