marco_patino

6 ms·

1. 1.▲
   by marco_patino 2y ago

   yep this all these points are fake. Same post as this flagged one: https://news.ycombinator.com/item?id=40983866 Pleas HackerNews do something
2. 2.▲
   by marco_patino 3y ago

   Now the GitHub repo has been disabled by GitHub due to violation of GitHub's terms. https://github.com/tukaani-project/xz
3. 3.▲
   Show HN: Allowing threads on GitHub PR Issue comments(blog.pullpo.io)

   27 points by marco_patino 3y ago|1 comments
4. 4.▲
   by marco_patino 3y ago

   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 swit
5. 5.▲
   Show HN: PR Template Builder(pullpo.io)

   2 points by marco_patino 3y ago|1 comments
6. 6.▲
   by marco_patino 3y ago

   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 v
7. 7.▲
   by marco_patino 3y ago

   Most of the devs actually love it, and they have excellent customer support. I you suggest a feature, they'll probably do it.
8. 8.▲
   by marco_patino 3y ago

   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
9. 9.▲
   by marco_patino 3y ago

   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 s
10. 10.▲
    by marco_patino 4y ago

    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'r
11. 11.▲
    by marco_patino 4y ago

    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.
12. 12.▲
    by marco_patino 4y ago

    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.
13. 13.▲
    by marco_patino 4y ago

    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, w
14. 14.▲
    by marco_patino 4y ago

    Sure! Let me know what your coworkers think as well. You can reach out to me at marco@pullpo.io.
15. 15.▲
    by marco_patino 4y ago

    Thanks for the comment! Yes, and when the pull request is merged or closed, the Slack channel is automatically archived.
16. 16.▲
    Show HN: Pullpo – Code review conversations on Slack(pullpo.io)

    23 points by marco_patino 4y ago|13 comments