Rob Pike
Co-creator of the Go programming language, of UTF-8 and of the Plan 9 operating system; formerly of Bell Labs.
Rob Pike did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.
Filter All topics · Newest first
-
Their wordsa small package with good intentions can accumulate both a large set of dependents and a large set of dependencies, turning it into a vector for bloat and malfeasance.
- 13 months earlier
-
Their wordsIt's a mistake common to engineers everywhere to confuse the solution and the problem like this.
↗What We Got Right, What We Got Wrongcommandcenter.blogspot.com 1st of 3 in this piece
-
Their wordsIt's important, though, whatever concurrency model you provide, to do it exactly once, because an environment providing multiple concurrency implementations can be problematic.
↗What We Got Right, What We Got Wrongcommandcenter.blogspot.com 2nd of 3 in this piece
-
Their wordsConcurrent code only goes faster when parallelized if the underlying problem is intrinsically parallel, like serving HTTP requests.
↗What We Got Right, What We Got Wrongcommandcenter.blogspot.com 3rd of 3 in this piece
- 4 weeks earlier
-
Their wordsComplexity is multiplicative. In a system, like Google, that is assembled from components, every time you make one part more complex, some of the added complexity is reflected in the other components.
↗Simplicitycommandcenter.blogspot.com 1st of 3 in this piece
-
Their wordsBut complex systems are NEVER fast-they have more pieces and their interactions are too poorly understood to make them fast. Complexity generates inefficiency.
↗Simplicitycommandcenter.blogspot.com 2nd of 3 in this piece
-
designsimplicitysoftware performance
Their wordsBecause of the multiplicative effects of complexity, getting 2% performance improvement by adding 2% complexity-or 1% or maybe even .1%-isn't worth it.
↗Simplicitycommandcenter.blogspot.com 3rd of 3 in this piece
- 15 months earlier
-
Their wordswhat we learn through our education has always been filtered by those who came after the events.
↗My black body story (it's physics).commandcenter.blogspot.com