Long time no post. Here's my attempt to illustrate the before-and-after experience of coding and testing at Google in light of the work done by the Testing Grouplet, Testing Tech, Build Tools, Engineering Productivity, and the Fixit Grouplet.
3 plus ones
Shared publicly•View activity
- I was surprised to see in the 2006 version where you wrote "The build system is very permissive when it comes to build input sources; not all of them have to be safely version-controlled within Perforce. " I understand that it reduces the time spent but it sounded like it would be very frustrating when trying to find where an input originated from. I'm enjoyed reading your post thanks fro giving me an inside look on how a Google engineer spends his time.Dec 2, 2011
- Wow, that's Yegge-ic in scope and detail. Count me as one of the newbies who never realized how bad things were back in the day. Perforce and Blaze are still Too Damn Slow, but not slow enough to justify a trip to the game room :-(.Dec 3, 2011
- No mention of C/J builds in the "Before" vs TAP in the "After" -- this was the #1 boffo contribution of TAP. Oh, next time remind me to tell you about SIERRAP...Dec 5, 2011
- I agree with you, though I hope the value of TAP is clear even absent of any mention of Chris/Jay. I'd considered mentioning the Chris/Jay build, but left it out for two primary reasons. For one, a discussion of Chris/Jay also begs a discussion of the Unit Test Framework, which spawned Chris/Jay, just as Chris/Jay spawned One-Click and TAP. I could've mentioned the UTF, but I feared it would've made an already lengthy chapter even longer.
For another, Chris/Jay hadn't yet achieved its ubiquitous popularity by summer 2006; it wasn't until summer 2007 that the push behind Test Certified started in full-force which led to Chris/Jay adoption everywhere. By the same token, most folks didn't pay a lot of attention to the UTF by that point either. So in the interest of historical accuracy, and to underscore the end-to-end impact between not having a build (like the majority of Google in 2006) and then having TAP (like the majority of Google in 2011), I chose to hold onto Chris/Jay for a future post.
Now that I think about it, I'll draft "A Day in the Life of a Build Cop", also done in a narrative style, that will highlight the differences in continuous integration systems alone.Dec 5, 2011
- It's even easier to grok the awesomeness (and scale) of TAP when comparing it to how crappy and distributed and fragmented and fragile things were before it.Dec 5, 2011