Axolo mentions (9)

• Top 10 code smells every engineer should know to improve their pull requests

  After a few years of helping developers review code, I came up with 10 code smells and how to fix them while building my project Axolo. - Source: dev.to / 3 months ago

• 7 frustrations to avoid with code review best practices

  Between the PR creation until it’s merged, the majority of the time, nothing will happen. We wait for the next step to happen. Unfortunately, that idle time hurts the delivery time (the lead time for changes). While they wait for a review, developers will be tempted to start another task, leading to context-switching. Practicing mob programming can prevent such latencies. Also, a solution like Axolo offers a Slack... - Source: dev.to / about 1 year ago

• RoastMyLandingPage: DX by Axolo, give a voice to your developers

  Comments: We are launching a free side project to create awareness for our main service (https://axolo.co). Source: about 1 year ago

• Show HN: Pullpo – Code review conversations on Slack

  Looks really nice! Also I love the level of personality on the marketing page, it's nice to see a product not taking itself too seriously. Just curious, this seems to have a lot of overlap with Axolo (https://axolo.co/) and I always love chatting to new people in this space. Email in my bio if you want to say hi! - Source: Hacker News / about 1 year ago

• The three best ways to receive GitLab CI/CD & pipelines notifications in Slack

  Disclaimer: I built one of the tool with a friend (https://axolo.co), but even if it is not for you I hope the two others possibilites might help your team! Source: over 1 year ago

gitconvex mentions (0)