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.
It's impressive to see how Pullpo.io is aiming to streamline the code review process. Integrating directly with tools that developers already use daily like Slack and GitHub can certainly cut down on the time it takes to get feedback. I'm curious, does the platform offer analytics on code review times and outcomes to help teams improve their processes?
Upvoted for the potential to greatly accelerate development workflows.
@aman_wen Hey Aman! Yep :) The insights part is supper important. With Pullpo you can have objetive DORA metrics, but also we combine it with developer feedback gathered via Slack, so that you have an holistic view on the bottlenecks of your organization. You can have more info here:
https://youtu.be/_FsZy6-F3ys?si=...
@sentry_co Hey André! Good question!
Code reviews are all about collaboration and speed. It's a conversation that needs to happen fast because otherwise the team ships slower.
Achieving this level of collaboration on GitHub is imposible for many devs, their notification system is bad, and you can't have a real time written conversation (you have to refresh the page every time to see new messages)
With Slack, collaboration is much easier, you can configure which type of notifications and reminders you want to receive and you can have fluid conversations even using Slack's features likes huddles, audio messages etc...
Also, sometimes is useful to add non-devs to the channel too, like product designers, UI researcher or other stakeholders.
Anyway, all the conversation in synced in both places, and if the rest of your team uses Pullpo, you can still collaborate through github and opt out of Pullpo.
Hope it helped!
@marco_patino Personally I pipe all issues and all commits, prs etc. through slack. which is great. but we only use it for visibility. Nudge people to keep momentum up etc. Whatabout backtracking tho? having all PRs in GitHub enables you to retroactively go through how things unfolded. Slack is more ephemeral. most teams don't subscribe to slack and so history is forgotten after a few months etc.
@sentry_co Yep! Slack is more ephemeral thats right, but the cool thing is that Pullpo saves the conversation in both places: in the Slack channel but also in the GitHub PR 🕺
So if you want to go back and check old PRs messages, you can still do it in GitHub, even if the conversation happened in Slack!
@marco_patino Aha. So it's a 2 way sync? I would focus on that part in the marketing. Because that is where the power is here. Just call it 2-ways sync for your PRs. Discuss on GH or Slack. Bring in the rest of the non devs as well. etc etc
Congratulations on the launch!
+ clever name..octopus, an intelligent and capable animal that can make pull requests
+ video editing is off the hook. Presenter pulled a reverse Clark Kent and starts wearing glasses out of nowhere.
+ Posthog integration is smart.
@giri Hey! You mean microsoft teams? Yep we have a waitlist and teams is the next after we finish the Bitbucket integration next week. Please, fill this form and we will give more priority to the teams integration! https://pullpo.io/new-integrations
This tool seems really efficient for streamlining code reviews! I’m curious, does it support all programming languages, and is there a limit to the number of reviews one can do in the free option? Thanks for the innovation!
@oleksandra_vasiukhnyk Hey! Yes, Pullpo is language-independent! Although the code reviewer works better with the most common languages such as JavaScript, Java, Python...
On the free tier, Pullpo is free for up to 5 developers and is always free for open source projects. The number of code reviews is always unlimited.
Congrats on the launch, guys! At fermat.app, we were probably among the first bunch of users of Pullpo some months ago, and it’s incredible how the product has evolved since then. You have my purest upvote!
@kosmoz_glasskube It helps summarizing the PR and giving a initial review for issues that common linters don't catch well. Also, since it's well integrated with Slack we plan that you can interact directly with the AI in Slack (also in the github pr) and ask questions on the code, suggest solutions alternatives...
The objetive is the same: merge the pull request faster.
Replies
Pullpo.io
Pullpo.io
Pullpo.io
Pullpo.io
Pullpo.io
WebCurate
Pullpo.io
Pullpo.io
Pullpo.io
Pullpo.io
Videotok
Pullpo.io
Llanai
Pullpo.io
Pullpo.io
Pullpo.io
Pullpo.io
Explorer | Explore Human Knowledge
Pullpo.io
Tella
Pullpo.io
BoringCashCow
Pullpo.io
a1.art
Pullpo.io
Pullpo.io
Pullpo.io
Glasskube
Pullpo.io