marco_patino

yep this all these points are fake. Same post as this flagged one: https://news.ycombinator.com/item?id=40983866

Pleas HackerNews do something

Now the GitHub repo has been disabled by GitHub due to violation of GitHub's terms. https://github.com/tukaani-project/xz

In the first one or two weeks of their training, I recommend implementing pair programming. Pairing your junior developers with more experienced developers or you. One actively coding while the other provides guidance and support, then switch places. This hands-on collaboration can accelerate a lot the learning process.

After that, the best place to continue learning is on code reviews in PRs. As @half0wl mentioned, it's importat to do it in both directions: you review their code, they review your code. This feedback loop will help your junior developers learn best practices and gain a better understanding of the codebase.

To facilitate these code review conversations, I recommend utilizing a tool like Pullpo.io (https://pullpo.io/products/channels), It allows you to have more enriching code reviews quickly on Slack, without wasting much time and being able to merge the PR sooner.

That said, learning curves can vary for individuals, and it's crucial to foster an environment of continuous learning and growth. But if after two years they can't keep up, i think it may not be the right person

Totally agree! Code reviews are not only for 'making sure things don't blow up $$ in production.' If your team doesn't use pair programming, code reviews are the best opportunity to share knowledge and align vision and values across the team.

If you feel like code review conversations are taking too long and affecting your cycle time, then you can use the tool I created: https://pullpo.io to have these conversations on ephemeral bidirectional GitHub-Slack channels.

Most of the devs actually love it, and they have excellent customer support. I you suggest a feature, they'll probably do it.

there are like 3 devs that don't like it because they are used to the github way of doing things, they always have the github tab open and prefer not to have notifications in slack.

We disabled pullpo for these people. However they can still collaborate with the people that use pullpo. The comments they send to github are brought to slack too and viceversa.

Still, code reviews take 2 to 3 times less

We use https://pullpo.io. It's a GitHub-Slack integration that creates ephemeral slack channels per pr, with all the people involved in the pr.

The first code comments still happen in GitHub, but then those comments go to slack (with the code context) so that the code review conversation happens there.

Thank you for your positive feedback on our product and our marketing page! We believe that technology doesn't have to be dry or boring, and we try to infuse some personality into our brand whenever possible.

Regarding Axolo, we're aware of their product and there may be some overlap in functionality. However, we believe that our product offers a unique set of features and benefits that sets us apart, such as code comments with context, AI generated code reviews (and summaries) and lower pricing.

Thank you for mentioning your company, CodeApprove! I looks very nice too, I hate not being able to comment code that is not in the diff.

I'll definitely reach out!

Thanks! If you have any feedback or suggestions for us, please feel free to share them. We're always looking for ways to improve and enhance our product for our users.

That's fantastic to hear! We're thrilled that Pullpo has been useful to you and has improved your team's shipping cadence. It's always great to receive positive feedback and know that our product is making a difference.

Thank you for your feedback! We appreciate your positive comments and recognition of the value our product can offer.

Regarding your question about how our feature compares to GitHub's Slack bot, while there may be some similarities, with Pullpo, each pull request creates a dedicated Slack channel with all involved parties, and unlike the GitHub bot, only the relevant people are notified when a code review process starts. Then they can have the code review conversation in Slack, in a easy and fast manner.

As for our vision to make this a "10xer," we are constantly looking for ways to innovate and improve our product. We gather a lot of feedback from our users and discover new problems every week. Maybe someday we'll publish another post with the new solutions.

Thank you for trying out our product. We hope it helps streamline your code review process and enhances your team's productivity.

Sure! Let me know what your coworkers think as well. You can reach out to me at marco@pullpo.io.

Thanks for the comment! Yes, and when the pull request is merged or closed, the Slack channel is automatically archived.