Crucible 2 Beta Insight (part 2) – Iterative code review

With a sweet new UI designed to make code review as easy as email, the new beta of Crucible 2 is packed with great features. The most revolutionary of which is the idea of iterative code review.

With a sweet new UI designed to make code review as easy as email, the new beta of Crucible 2 is packed with great features. The most revolutionary of which is the idea of iterative code review.

Crucible 2 – Iterative code review

Most code review processes are naturally iterative. First you write some code, then one of your peers reviews it only find some way to improve it, and then you code it up again, and repeat as necessary.
Although this process may take just a few minutes, it’s not unusual for reviews to include 2 or 3 revisions. That’s why Crucible 2 has made it simple to manage reviews throughout this iterative process:

Iterative code review makes it simple for teams to collaborate around code changes in order to ensure the highest code quality. Next time, I’ll cover more the details of Crucible 2’s new Jira integration.

Give us your feedback

Download the public beta of Crucible 2 and check out the Crucible 2 Beta Release Notes for more information.
You can also check out these updated public instances:

Kick the tires yourself and let us know what you think.

Exit mobile version