Welcome to the third volume of Bear Tracks, the newsletter about peer code reviews, Code Collaborator, and other tidbits from Smart Bear Software. This issue of Bear Tracks features some exciting news about Code Collaborator and Smart Bear.
First - Code Collaborator v5.0 beta released just a couple days ago! Find out the details of the release and how you can get your own copy! And be sure to check out which conferences we're attending. Also in this volume, we present our third and final article in the Social Effects of Peer Code Review series, and you get to meet Brandon DuRette, one of our veteran developers and Code Collaborator team lead.
As always, if you have feedback, requests, or if you just want to say "hi," be sure to drop us a line.
Happy reading!
-- Hannah Jung
Table of Contents
1. Code Collaborator Version 5.0 Beta Available Now!
2. Free Webinar: Code Collaborator v5.0
3. Tips for Developers: Social Effects of Code Review, Part 3
4. Meet the Bears: Brandon DuRette
Code Collaborator Version 5.0 Beta Available Now!
This week, we're celebrating the beta release of Code Collaborator v5.0! In the new version, we support PDF and URL reviews, making this the most advanced code review tool yet. We also implemented tons of new features that will make reviewing your code easier than before.
If you want to try out the new Code Collaborator, download a trial to experience the new features yourself. And while you're at it, let us know what you think about it!
Free Webinar: Code Collaborator v5.0
Want to see Code Collaborator v5.0 in action? We will be hosting a FREE webinar on April 22 at 11:00 am CST where you will see a demo of the coolest new features in version 5.0. Space is limited, so register now!
Tips for Developers: Social Effects of Code Review, Part 3
by gregg sporar
In part 2 of this series, I listed some tips for managers who are trying to get a team to add peer code review to their software development process. Most of those tips were about setting the stage for successful reviews by outlining the right "tone" and defining expectations.
Tone is also important for developers who are doing peer code reviews. Specifically: the tone you use in your comments about a peer's code can make all the difference in the world.
But how can you get your point across during a review while using the correct tone?
Read the whole article...
Note: This is the final entry in a three-part series. The tips from all three entries are available in this recently published white paper: Improve Quality and Morale: Tips for Managing the Social Effects of Code Review.
Meet the Bears: Brandon DuRette
Brandon DuRette, our Senior Software Developer, leads the Code Collaborator development team. Always there to offer an insightful perspective, Brandon can help with almost any problem, technical or not. He's one of those guys everyone should know, so naturally, he's our featured bear for this issue!
Describe a day in the life as the Senior Software Developer of Smart Bear.
Mostly I spend my days writing code, but I also do code reviews and answer questions from other developers and help out with tech support on some issues.
Read more...
Deep Agile 2009
Are you in the Boston area? The Deep Agile 2009 conference is April 25-26 and is all about using Agile techniques to develop embedded systems. Smart Bear is a sponsor, so we can save you money! Just use discount code SmartBear_Emb_09 when you register.
Smart Bear Blog
Like our newsletter? Read our Smart Bear blog, which is dedicated to Code Collaborator how-to's, tips for your own code reviews, and random musings from Smart Bear employees. Take a look at some of our favorite articles featuring Code Collaborator tips.
Integrating with Static Analysis Tools
Please feel free to contact us with any questions, suggestions, or comments regarding the newsletter or just about anything! Got a funny story during your code reviews? Please share it with us.
Feature Your Blog Here
Do you have a blog? Blog about us and we'll send you a free Smart Bear shirt. And we might even link to your blog from our website.
