What Google Taught Me About Scaling Engineering Teams

Re:What Google Taught Me About Scaling Engineering Teams by danso on Wednesday June 18, 2014 @11:27PM (#7914251)

> One reason I was able to quickly become productive within Google was because the company had invested so many resources into training documents called codelabs. Codelabs covered the core abstractions at the company, explained why they were designed, highlighted relevant snippets of the codebase, and then validated understanding through a few implementation exercises. Without them, it would’ve taken me much longer to learn about the multitude of technologies that I needed to know to be effective

Any Googler care to share what a "codelab" looks like? Always interested in seeing innovations in documentation/onboarding (and I'm guessing it has nothing to do with the now retired "Code Labs"? https://code.google.com/labs/)

[ Parent | on HN ]

Re:What Google Taught Me About Scaling Engineering Teams by jrockway on Thursday June 19, 2014 @03:50AM (#7914895)

We have some public codelabs; the Dart ones come to mind first:

https://www.dartlang.org/codelabs/darrrt/

Basically, a tutorial. The internal codelabs have some logic to substitute your username throughout the text (good for things like "create a test directory"), but are otherwise very similar to the public ones.

[ Parent | on HN ]

Re:What Google Taught Me About Scaling Engineering Teams by skj on Wednesday June 18, 2014 @11:31PM (#7914284)

Nothing fancy, just a start-to-finish tutorial.

[ Parent | on HN ]

Re:What Google Taught Me About Scaling Engineering Teams by chrisbroadfoot on Thursday June 19, 2014 @12:33AM (#7914492)

They're a bit like Android's training guides, which I think are excellent: https://developer.android.com/training/index.html

[ Parent | on HN ]