DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

Discussion on: The Code Review Checklist βœ…

prowe214 profile image
Paul Cullen Rowe Author

I have not, those sound interesting! I have always organized my teams in either application specific or feature specific groups. This generally makes picking the reviewers easy β€” pick those people, plus any technical manager or architect who may be involved in overseeing the whole production across teams.

Thread Thread
heroincommunity profile image
German Chyzhov

Yes, feature teams is a one way to solve the problem. However, as a developer, I could say, that sticking the whole team to a fixed set of features often leads to lower retention rate.
If in other case, the developers are not sticked to a sed of features, then there could be a mess with responsibility: "who owns XXX" question start appearing often in chats.
As mention-bot is dead and CODEOWNERS is static, I decided to create my own automatic recommendation tool.
Feel free to contact me in Linkedin if interested.