Note: I wrote this post for an internal team blog, but thought it was worth sharing more widely. Part of getting to good code reviews is some up front discussion about trade-offs and implications for bigger architectural changes. I think of code review as when “my” code becomes “our” code – for architecture, those conversations…