For episode 20, we tackle the topic of tooling proficiency on your release engineering, ops, and development teams, specifically through the lens of version control tools. Version control is becoming a ubiquitous part of the “DevOps movement,” and we talk through what level of understanding should be expected, what level of training should be provided, and whether those are different for different teams or different tools. Plus, we poke a lil’ fun at git, as we try to answer:
Join J. Paul Reed, aka @SoberBuildEng, Youssuf El-Kalay, aka @buildscientist, Sascha Bates, aka @sascha_d, and EJ Ciramella, aka @eciramella, plus the last couple of weeks in News & Views and a new Tool Tip!
- 1:18 – News & Views
- 1:20 – Rogue gaming studio employee slips bitcoin mining software into a release
- 1:33 – Ricon East!
- 2:35 – How Github “democratizes the process of shipping“
- 6:09 – One Microsoft kernel developer’s perspective on (the cultural reasons?) behind why NT is slower than other operating systems
- 9:15 – 42 Floors’ “Precation” policy
- 15:24 – Main Segment: Does Your Entire Team Have to Git It?
- 19:56 – “Just use git flow“
- 28:37 – The “free Git book“
- 29:13 – Rhodecode
- 30:08 – “We don’t use any version-control services or systems.”
- 37:09 – On inconsistencies in the cognitive model of git’s “porcelain”
- 44:52 – Tool Tip
- 47:03 – RELENG 2013 Workshop in San Francisco coming up
Do you run into lack-of-proficiency with version control or other tools with teammates? Does it slow your team down? Is there a point in having “integration engineers” or “tool/language lawyers” anymore?
Join the discussion!