“One of my guiding principles is, “Don’t do anything that other people are doing.””
Seymour Cray offered this line in a Computer History Museum history of his supercomputer designs. Cray repeatedly pursued the fastest practical computers of his era, often with small teams and unusual architectural choices. He tried to stay away from crowded development paths where incremental imitation would prevent the concentrated work required for a real performance breakthrough. The source makes clear that the remark grew from experience, not from a prediction made at a distance.
The principle treats differentiation as a research strategy. If an established approach already has many capable practitioners, a small team may contribute more by exploring a neglected constraint, architecture, or implementation technique. Put into practice, the idea changes what a team measures and which tradeoffs it is willing to defend. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
Novelty is not automatically value. Refusing to repeat proven work can create avoidable risk, and even Cray’s machines depended on established physics, manufacturing, software, and customer needs. Difference must answer a consequential problem. A careful application therefore asks where the analogy stops as well as where it illuminates. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Technology markets reward fashionable duplication, especially when funding follows visible trends. Cray’s challenge is to identify where orthogonal work can change the frontier, then prove the difference with measurements rather than marketing language. Applied carefully, the idea helps teams turn historical insight into choices that can be tested and revised. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Seymour Cray offered this line in a Computer History Museum history of his supercomputer designs. Cray repeatedly pursued the fastest practical computers of his era, often with small teams and unusual architectural choices. He tried to stay away from crowded development paths where incremental imitation would prevent the concentrated work required for a real performance breakthrough. The source makes clear that the remark grew from experience, not from a prediction made at a distance.
The source record connects the wording to a Computer History Museum history of his supercomputer designs, which is the context used for this post.
The principle treats differentiation as a research strategy. If an established approach already has many capable practitioners, a small team may contribute more by exploring a neglected constraint, architecture, or implementation technique. Put into practice, the idea changes what a team measures and which tradeoffs it is willing to defend. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
The interpretation focuses on a decision or design principle that readers can test against actual systems.
Novelty is not automatically value. Refusing to repeat proven work can create avoidable risk, and even Cray’s machines depended on established physics, manufacturing, software, and customer needs. Difference must answer a consequential problem. A careful application therefore asks where the analogy stops as well as where it illuminates. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Technology markets reward fashionable duplication, especially when funding follows visible trends. Cray’s challenge is to identify where orthogonal work can change the frontier, then prove the difference with measurements rather than marketing language. Applied carefully, the idea helps teams turn historical insight into choices that can be tested and revised. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.