3 ms·

Yes; Google hiring people with a history of innovation and giving them the support (financial and otherwise) to undertake a project does make the project part o

by akerl_ 6y ago

Yes; Google hiring people with a history of innovation and giving them the support (financial and otherwise) to undertake a project does make the project part of Google’s engineering portfolio. I’m not sure how this could be in dispute. It’s not like Golang was something that Google backed on Kickstarter: they gave resources and pay to the people whom they intentionally hired because they wanted engineers with their skillset. If employees hired as engineers, who work on engineering projects, don’t count as part of your company’s “engineering ethos” just because they were already engineers before you hired them, I’m not sure we have a shared agreement on what “engineering ethos” means. Are only fresh college graduates permitted to count as part of your “ethos”? How many years of experience can an engineer attain before their accomplishments at work are no longer part of their employer’s ethos?

ddevault 6y ago
I must be really awful at explaining my point or there's an awful lot of willful ignorance in this thread. Either way, something awful is going on. Read carefully: the engineering culture of Google - it's practices, policies, principles, insiprations, and so on - did not make Go. The prior experiences of the Go authors, and a handful of specific and obvious influences, both of which are objectively not of Google, made Go. Google's engineering ethos does not get credit for Go, though maybe an argument can be made that their wallet gets credit. Personally, I don't agree with that, but it's beside the point.
- akerl_ 6y ago
  The part that I don’t understand is: why does Google not get credit, in your opinion, for having built an engineering org from qualified people? Google hired the engineers who made Go. A company’s engineering ethos is the combined ethos of its engineers. The Golang developers are engineers who Google hired. To attempt to draw a metaphor: if I operated an auto repair shop, and I wanted my shop’s “ethos” to be “we do high-quality repairs on cars”, one of the primary ways to do that would be to hire smart, already-experienced mechanics. And it would seem strange to me if people wrote blog posts saying that the work of those mechanics didn’t count towards my “ethos” because they were already good at their jobs; that’s why I hired them! As a tangential comment, phrases like “Read carefully” seem extraneous, as does the accusation of “an awful lot of willful ignorance”. They just serve as jabs at the other commenters here.
  - ddevault 6y ago
    Go was principally made by 3 people, whose resumes basically justified being allowed to work at their discretion (this last bit is conjecture, but I would be surprised to be proven wrong). If Ken Thompson has a manager at Google that has any influence whatsoever on Ken's work, then Google's culture is more broken than I thought. The rest of Google is over 100,000 engineers who have managers, team leads, and much more rigid policies and workflows than I imagine the Go designers were ever subjected to during the development of Go. This is the engineering ethos to which I refer, not the system to which the Go designers where subject. So: Google gave a chair and a desk to a few talented people who applied experience and influences from entirely outside of Google to designing a programming language. In my book, Google doesn't get credit for that, and their engineering culture definitely doesn't get credit for that - it was barely involved, if at all.
    - akerl_ 6y ago
      It seems like you’re making a couple of key assumptions about what the work environment looks like for the core Golang dev team, and then extrapolating from there to exclude them from your definition of Google’s “ethos”. Separately, the idea that a manager having influence on a good engineer’s work is “broken” is one I don’t understand. But I think, based on this comment thread, it’s unlikely we’re going to reach a consensus.
    - googthrowaway42 6y ago
      FWIW I am an ex-Googler and I agree with you. The principal authors of Go are not really Googlers in the sense that other "mere mortals" are. Their engineering skills, practices, and decisions are not informed or subject to the strictures of the wider culture at Google.
      - akerl_ 6y ago
        To help me understand, can you give an example of the kind of stricture that applied to other engineers but not to the Golang core team?

by akerl_ 6y ago

ddevault 6y ago

I must be really awful at explaining my point or there's an awful lot of willful ignorance in this thread. Either way, something awful is going on. Read carefully: the engineering culture of Google - it's practices, policies, principles, insiprations, and so on - did not make Go. The prior experiences of the Go authors, and a handful of specific and obvious influences, both of which are objectively not of Google, made Go. Google's engineering ethos does not get credit for Go, though maybe an argument can be made that their wallet gets credit. Personally, I don't agree with that, but it's beside the point.

akerl_ 6y ago
The part that I don’t understand is: why does Google not get credit, in your opinion, for having built an engineering org from qualified people? Google hired the engineers who made Go. A company’s engineering ethos is the combined ethos of its engineers. The Golang developers are engineers who Google hired. To attempt to draw a metaphor: if I operated an auto repair shop, and I wanted my shop’s “ethos” to be “we do high-quality repairs on cars”, one of the primary ways to do that would be to hire smart, already-experienced mechanics. And it would seem strange to me if people wrote blog posts saying that the work of those mechanics didn’t count towards my “ethos” because they were already good at their jobs; that’s why I hired them! As a tangential comment, phrases like “Read carefully” seem extraneous, as does the accusation of “an awful lot of willful ignorance”. They just serve as jabs at the other commenters here.
- ddevault 6y ago
  Go was principally made by 3 people, whose resumes basically justified being allowed to work at their discretion (this last bit is conjecture, but I would be surprised to be proven wrong). If Ken Thompson has a manager at Google that has any influence whatsoever on Ken's work, then Google's culture is more broken than I thought. The rest of Google is over 100,000 engineers who have managers, team leads, and much more rigid policies and workflows than I imagine the Go designers were ever subjected to during the development of Go. This is the engineering ethos to which I refer, not the system to which the Go designers where subject. So: Google gave a chair and a desk to a few talented people who applied experience and influences from entirely outside of Google to designing a programming language. In my book, Google doesn't get credit for that, and their engineering culture definitely doesn't get credit for that - it was barely involved, if at all.
  - akerl_ 6y ago
    It seems like you’re making a couple of key assumptions about what the work environment looks like for the core Golang dev team, and then extrapolating from there to exclude them from your definition of Google’s “ethos”. Separately, the idea that a manager having influence on a good engineer’s work is “broken” is one I don’t understand. But I think, based on this comment thread, it’s unlikely we’re going to reach a consensus.
  - googthrowaway42 6y ago
    FWIW I am an ex-Googler and I agree with you. The principal authors of Go are not really Googlers in the sense that other "mere mortals" are. Their engineering skills, practices, and decisions are not informed or subject to the strictures of the wider culture at Google.
    - akerl_ 6y ago
      To help me understand, can you give an example of the kind of stricture that applied to other engineers but not to the Golang core team?