meta_pixel
Tapesearch Logo
Log in
Coding Blocks

Source Control Etiquette

Coding Blocks

Allen Underwood, Michael Outlaw, Joe Zack

Technology, Careers, How To, Business, Education

4.91K Ratings

🗓️ 12 October 2013

⏱️ 56 minutes

🧾️ Download transcript

Summary

This episode is all about source control etiquette. It’s a bit different from the last two podcasts we released and we’d love to hear how you liked it! Subscribe on iTunes or Stitcher and make sure to send us your feedback! Show Notes Duration ~56 Discussion on Source Control Etiquette 00:00 – 25:09 A tale […]

Transcript

Click on a timestamp to play from that location

0:00.0

You are listening to coding blocks episode 3.

0:06.0

Subscribe to us on iTunes, Stitcher, and more using your favorite podcasting app

0:10.4

and be sure to leave us a review on iTunes or Stitcher or wherever you happen to have found us.

0:15.0

And also don't forget to check us out at codingblocks.net, where you can find show notes, examples, discussion, and much more.

0:22.0

Send us your feedback, question, and rants to comments at

0:26.2

codingblocks.net.

0:28.0

And with that, welcome to coding blocks. I'm Michael Outlaw. I'm Alan Underwood, and I'm

0:32.4

Joe Zach. And we've gathered around the proverbial water cooler to discuss source control today.

0:38.0

That's right in today's episode we're going to step away from the keyboard and take our propeller hats off and stay out of the weeds if possible.

0:46.4

And without further ado, I want to start off with a story.

0:50.4

All right? So there was a situation where another person wanted to commit some stuff that they were working on.

1:00.0

And they were convinced that their stuff was fine, it was all good, but there was a compiler.

1:06.0

They couldn't compile.

1:08.0

And this person was adamant on committing the code and pushing it into the main repository because it was not their problem and whatever.

1:18.6

And I was taking the stance that no, no, no, no. Even if it wasn't you know any fault of yours

1:25.8

you've now found it it's your responsibility you you should do the honorable thing

1:30.7

and correct it you shouldn't knowingly commit it if you know that there's a problem there.

1:37.0

And we went back and forth on it until finally, lo and behold, we found out, oh, it did turn out to be a problem that was newly introduced

1:45.3

and got fixed beforehand so it reluctantly the compile error was fixed and prior to the commit was being pushed into the main repository.

1:57.0

But it brought me into this, you know, greater concept here where is the moral of the story being you should not

2:07.2

knowingly commit broken code so let me get the straight so we've got maybe the build wasn't working when they got started but how you know how do you test your code if you can't compile it?

2:19.3

Yes, and that is a very valid question.

...

Please login to see the full transcript.

Disclaimer: The podcast and artwork embedded on this page are from Allen Underwood, Michael Outlaw, Joe Zack, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of Allen Underwood, Michael Outlaw, Joe Zack and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.

Copyright © Tapesearch 2026.