Hello from Barcelona! Marco here, cofounder of Pullpo.io.
For the past year, my co-founder Cesc and I were very focused on one specific thing: code reviews. We analyzed and interviewed dozens of teams of different sizes, industries, and countries to truly understand the best practices surrounding code reviews. This is what we know for sure:
CODE REVIEWS NEED TO BE FAST.
We should optimize for the speed of shipping features as a team, not for the speed at which an individual developer can write code. This means replying ASAP to code review messages! Here is how Pullpo helps:
- 1 PR = 1 temporal Slack channel (always in sync with GitHub/GitLab/BitBucket)
- AI PR summary and first review
- Custom notifications on all relevant and actionable events
- Custom reminders on team objectives
- Squad channels to receive PRs and reminders
- DORA Metrics to track team improvement
CODE REVIEWS SHOULDN'T BREAK YOUR FLOW.
This is also important: If you are super focused in the middle of a task, finish the task first, then reply to the code review. Interrupting that flow state with a context switch will be less efficient for you individually and for the team as well. This is how Pullpo helps:
- Reduced noise: only relevant, actionable notifications.
- All notifications are customizable in Pullpo and in Slack.
- Customizable objectives and reminders.
CODE REVIEWS ARE (ALMOST) ALWAYS IMPORTANT.
Depending on the industry, sometimes super simple changes don't require code reviews. But in general, code reviews are very important, not only for ensuring that the code meets the requirements for all stakeholders, but also as an important process for learning and defining the culture of the company. This is how Pullpo can help:
- Add all stakeholders to the channel: product people, UI desingners, owner, reviewers..
- Communicate better with all Slack functionality: huddles, audio messages, screen recordings and more!
Would love to know your thoughts!
Marco.
