Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There's a really good code review guide on the plaid blog that addressed this: https://blog.plaid.com/building-an-inclusive-code-review-cul....

Money quote: "Nothing should be surprising to a reviewer in a code review: discuss any significant design decisions before code is written. Code reviews are a time to iron out implementation details, not discuss major design or architecture decisions."



What if you use pull requests to prototype architectural change? My take is your pull request should include the context of the change and the sort of feedback you want.


I think that explicitly noting “this isn’t ready, but I’d like to discuss x,y,z” ought to cover it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: