> From the outside, you just can't imagine how few Google engineers are responsible for how many products and data integrations. I mean, from one perspective,

> From the outside, you just can't imagine how few Google engineers are responsible for how many products and data integrations. I mean, from one perspective, sure, it'd be nice if there were a team of thousands to handle this problem. But from another perspective, you just said there were a dozen people staffed to handle a single feature of a single product. Out of how many features, out of how many products? My first job was at a start up back in the comparison shopping era where our goal was to get every product for sale on the internet into one place. For several years, I was responsible for all of indexing and search; another engineer was responsible for everything related to the front-end, another for everything related to crawling and scraping, and a forth worked on a variety of projects. Four engineers to cover every store's inventory in the world. So, you know, coming from that world, the idea that there are a dozen people responsible for just business hours is crazy. (For completeness, our engineering team fluctuated as high as a dozen when the company was flush with investor cash, down to four for a long stretch when the company went bankrupt for awhile, and then up to a half dozen or so when the company was profitable for a span.)