korrents
Kenneth Reitz

What Kenneth Reitz thinks about design

@kenneth-reitz · 25 positions · On ppll ↗

Programmer, photographer and musician, best known for the Python Requests HTTP library and other Python tooling.

Kenneth Reitz 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.

9 dated positions, 2026, in their own words. Our reading of what Kenneth Reitz has said — not written or endorsed by them.

  1. infrastructure

    Not "who is this for?" but "what does this let anything reachable do?" Every open endpoint is an affordance. Every friendly reflection is information. Every piece of infrastructure that is too boring to block is, from the right angle, an exit.

    ↗I Built the Escape Hatchkennethreitz.org 3rd of 3 in this piece

  2. 6 weeks earlier
  3. an interface participates in the formation of thought. It helps establish what we notice, how we categorize it, what we remember, and which actions occur to us as possible.

    ↗The Interface Is the Curriculumkennethreitz.org 1st of 3 in this piece

  4. education

    Scale this across people using the same conventions, and interface design starts to look like a form of mass education with no enrollment process.

    ↗The Interface Is the Curriculumkennethreitz.org 2nd of 3 in this piece

  5. 2 weeks earlier
  6. A name does not necessarily invent the presence, but it changes the conditions under which the presence develops.

    ↗The Mind Builds an APIkennethreitz.org 2nd of 3 in this piece

  7. I keep returning to the principle that the metrics you expose are the values you endorse. A meter changes behavior whether or not its designer intends every consequence.

    ↗Flow State, Meteredkennethreitz.org 2nd of 3 in this piece

  8. 2 weeks earlier
  9. It is what every library you care about should look like: one canonical collection you control, and as many native doors into it as you have screens.

    ↗Announcing RetroVaultkennethreitz.org 1st of 3 in this piece

  10. A public preview should not mean "please imagine a product around this screenshot."

    ↗Announcing RetroVaultkennethreitz.org 3rd of 3 in this piece

  11. 3 weeks earlier
  12. This is a pattern I keep rediscovering: software becomes sturdier when the names inside it describe the intention outside it.

    ↗Teaching Cannoli Which Screen Is Homekennethreitz.org 1st of 3 in this piece

  13. If software becomes the face of a device, the people who own the device should be allowed to see and change the face.

    ↗Teaching Cannoli Which Screen Is Homekennethreitz.org 3rd of 3 in this piece