18: Why and How We Review Code as a Team episode artwork

EPISODE · Mar 24, 2017 · 40 MIN

18: Why and How We Review Code as a Team

from It Depends · host Clear Function

On this episode, Daniel, Jesse, Mo, and Brian discuss the importance of reviewing code. What are some good tools for the code review process? How early is too early to get feedback on your code? Listen in to here answers to these questions and more. And, we introduce the "It Depends" bell on this one! ##Things Mentioned Imposter Syndrome episode The bus problem Github Atlassian Crucible GitLab merge request templates Ruby Mine IDE Gerrit Code Review For more information, check out our website at clearfunction.com. Follow us on Twitter at @clearfunction.

Episode metadata supplied by the publisher feed · Published Mar 24, 2017

Embed this episode

On this episode, Daniel, Jesse, Mo, and Brian discuss the importance of reviewing code. What are some good tools for the code review process? How early is too early to get feedback on your code? Listen in to here answers to these questions and more. And, we introduce the "It Depends" bell on this one!

Distinct summary based on available episode metadata or transcript content.

NOW PLAYING

18: Why and How We Review Code as a Team

0:00 40:34

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

No similar episodes found.

No similar podcasts found.

Frequently Asked Questions

How long is this episode of It Depends?

This episode is 40 minutes long.

When was this It Depends episode published?

This episode was published on March 24, 2017.

Can I download this It Depends episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.
URL copied to clipboard!