PullReview: Reach your Ruby Code Skill Walhalla

TL;DR: PullReview is close to Beta now. In this post we’ll show you the ease of use, the code reviews, and how PullReview guides you to become a better Ruby developer.

Some weeks ago, we lifted a small part of the veil on PullReview, our automated code review tool for Ruby on Rails in Github. We told you why we are in this game: you’re a programming hero, and we want to provide everything to be the most magnificent one you can be.

Valhalla

We think Code Review is essential – programming life blood. That is why we are developing PullReview. As our Alpha testers have driven us to a design we’re very comfortable with, we’re ready to show you some snippets of our Alpha version.

This post has two goals: we want to show to you how PullReview is moving along, and we want to get you so curious that you’ll sign up to the mailing list: you’ll be on the front row when we go into Beta , we’ll have a shot at convincing you how PullReview is your new bestfriend for Ruby on Rails Code Review.

Now that we’ve been completely open about that, let’s get to business. What will PullReview be doing for you? Two hints:

• A Hero should be a Hero
• Every Hero’s got a Learning Curve.

A Hero should be a Hero

What do we mean by that?

You should focus on your core: delivering great – smooth functioning – features to your users. Not setting up servers and installing a plethora of tools. Your time – and your flow – is too precious.

The God Thor does not wait for the next train to get to his adventures.

Equally, in programming, being the best you can be does nòt mean wasting time on coding activities that have nothing to do with your core competencies. That’s why PullReview is SaaS – that’s why we have tried incorporating all relevant analysis in one tool.

Simplicity starts at the sign up/login level:

  • Sign Up to PullReview 
  • Log in to PullReview using your Github account
  • Sync with your Github account
  • Pull your Branches and click “review”

Simple.

PullReview Review Screen

For the same reason, we put the most relevant Static Code Analysis tools under one hood. Once you pull a branch from Github to PullReview, PullReview analyzes your code for the following threats:

  • General Code Smell
  • Duplication
  • Complexity
  • Design
  • Style
  • Documentation
  • Test Infection

PullReview Analytics

PullReview separates the issues encountered in alternative categories, looking at different aspects:

  • the ease of fixing a problem
  • the gravity of a problem
  • how you have progressed in fixing previous problems

This way you get a good overview of the road you’ve travelled, the direction you’re taking now, and the one you should take.

Every Hero’s got a Learning Curve

Everyone needs to learn, and Everyone needs to Learn at his or her own pace.

That’s why PullReview – for starters – doesn’t just tell you what is wrong in your code: it tells you what to do to make your code better. Every time you have pulled a review, you can click each problem and see explained what is wrong exactly, and what fix PullReview proposes.

PullReview expanded review and code guidance

Not the what, but the how and the why. That’s how we all learn best.

Secondly, everyone has his or her very own flow. It is exactly this flow that makes it a real pain in the *#$ to find a reviewer you can trust at a moment in time that suits your way of working. PullReview is ready when you are. Not only does PullReview’s availability help you improve more constantly, you can focus your time with your Peers for the larger challenges at hand: for the details that render your project truly magnificent.

PullReview Github Repositories Overview

Cutting a long story short, this is PullReview:

  • Code Reviews, right away
  • The most relevant static analysis, all in one place
  • True Code Reviews, guiding you to improve your coding
  • Reviews at your pace, making room for True Peer Review when necessary

We are ready to help you in becoming a truly great programmer. Are you?

Yes? Only one answer: subscribe to the Beta!

As a final – important – note: we have everything to thank our Alpha testers for. They challenge us – day after day – to come up with the best Ruby Code Review we can deliver. Thank you all, it’s been – and still is – an exhilarating ride!

We hope this post has tickled you to be the best you can be, we can only hope that PullReview will play a part in your journey!

 

Enhanced by Zemanta




6 thoughts on “PullReview: Reach your Ruby Code Skill Walhalla

    1. Martin Post author

      Hi. We do not run your unit tests, we’re doing static analysis of the code. Some of our checks are specific to Rails, but not that much. We evaluate various kind of problems like style, security, code smells or even some design bad practices.

      Martin

      Reply
    1. Martin Post author

      Hi Andrew,
      This is a part of what we want to achieve: group tools and practices that we (as a community) know and like, and make them better together. I like as much as any developer to tweak my own settings, but at the end of the day, I want to spend my time delivering features and value – not installing tools.

      Having this kind of tools centralized also means that our whole (three persons) team use them the same way, and that no one forget to run them.

      Martin

      Reply
  1. Pingback: We’re at Arrrrcamp! (and you should, too) | 8th color

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>