3 ms·
Google's system is promotion-by-committee. It ends up having the same pros and cons as any committee-based system. On one hand, it avoids the kind of egregious
by kentonv 12y ago
Google's system is promotion-by-committee. It ends up having the same pros and cons as any committee-based system. On one hand, it avoids the kind of egregious mistakes and crimes that occur when too much power (i.e. to promote others) is vested in individual people (e.g. managers). On the other hand, committees are risk-adverse and will shy away from controversial actions. People who do good work following expected patterns get promoted. People who do controversial work, or who don't fit into an obvious mold, will have a tougher time, as a committee that can't come to agreement will default to no action.
- yid 12y ago> or who don't fit into an obvious mold, Genuine question: is that why you went in a completely different direction with Capn'proto than protobufs?
- kentonv 12y agoHmm, not sure I exactly understand the question. But I think the answer is probably "no". Cap'n Proto's design came mostly out of someone asking me one day whether two processes could share a protobuf object via shared memory, without serializing and parsing. I found the question interesting enough that I kept thinking about it and that eventually evolved into a design. My reasons for leaving Google had nothing to do with any of this, but gave me a well-timed opportunity to work on it. I actually primarily quit to do sandstorm.io, and did Cap'n Proto more on a lark, although it turns out to be really useful infrastructure on which to build Sandstorm.