Skip to content
quotesby

About this quote

What does it mean?
The speaker argues against enforcing orthogonal design purely for its own sake.
In plain terms
I don't like orthogonality just for the sake of being orthogonal.
What can you take from it?
Prioritize practical design over unnecessary abstraction.

Where it applies

  • software architecture
  • product design

Putting it to work

  • avoid over‑engineering
  • focus on real benefits

Questions to consider

  • When is orthogonality worth the extra effort?

Another view

Sometimes orthogonal designs do improve clarity and maintenance.

More from Larry Wall

  1. My arthritic pinkies are already starting to ache just thinking about ||||=.

    Permalink to quote #221
  2. Must be a different Larry Wall. There are at least 137 of us in the U.S.

    Permalink to quote #223
  3. But I know what's important to me, and what isn't. And I think I know what people can get used to, and what they can even learn to like. (It just takes some pe…

    Permalink to quote #220

Related quotes

  1. Architects know that some kinds of design problems are more personal than others. One of the cleanest, most abstract design problems is designing bridges. Ther…

    Paul GrahamPaul Graham quote #1
  2. The best thing software can be is easy, but the way to do this is to get the defaults right, not to limit users' choices.

    Paul GrahamPaul Graham quote #2
  3. Simple things should be simple, complex things should be possible.

    Alan KayAlan Kay quote #4