3 ms·

> Are you saying all of those projects at Google are owned by individuals who don't spend time interacting with others on the codebase No. That's not a reasona

> Are you saying all of those projects at Google are owned by individuals who don't spend time interacting with others on the codebase No. That's not a reasonable interpretation of anything I said. All the programs I mentioned are written by groups of people. Despite that if you measure each hour in their day and classify it as "in front of a machine" vs "in front of people" you will find nearly all are in the first category. Now if you further sub-divide "in front of a machine" and classify time by "time spent in a text editor coding" vs "time spent emailing, filing tickets etc" then most time will still be in the first category, unless something has gone badly wrong at Google since I left. Interactions with people are, in programming projects like that, a means to an end. Usually the end being some concrete outcome like a machine allocation or a cross-check for bugs. There may sometimes be design or brainstorming sessions, MapReduce being famously designed over many cups of coffee between Jeff Dean and his colleagues like Sanjay Ghemawat. But these conversations are entirely work focused. They aren't about people or relationships. And the time spent drinking coffee whilst figuring out the design is ultimately dwarfed by the long term effort required to build and maintain the software itself.

Apocryphon 9y ago
Coding in of itself isn't a highly social activity, but you still need people who are reasonably competent socially to be able to handle a project that requires teamwork. Just because communication and social interaction is a means to an end doesn't mean they can be excessively devalued. Sure, you can say time spent in front of a machine is the value center, and time spent interacting with others (in interminable meetings, at stand-ups, etc.) are cost centers. But it's generally accepted around here that neglecting cost centers is a strategic miscalculation, no?

Apocryphon 9y ago

Coding in of itself isn't a highly social activity, but you still need people who are reasonably competent socially to be able to handle a project that requires teamwork. Just because communication and social interaction is a means to an end doesn't mean they can be excessively devalued. Sure, you can say time spent in front of a machine is the value center, and time spent interacting with others (in interminable meetings, at stand-ups, etc.) are cost centers. But it's generally accepted around here that neglecting cost centers is a strategic miscalculation, no?