kennethreitz.org/data/themes/for-humans-philosophy.md

The "For Humans" Philosophy

Fifteen years ago, I wrote a Python library that made HTTP "for humans." The idea was simple: complex capabilities should be accessible through interfaces that match how people actually think, not how machines process information. That principle turned out to apply to everything — marriage, mental health, AI collaboration, community design.

Every technical choice embeds values about how humans should relate to technology. The "for humans" philosophy is just the insistence that those values should favor the human.

Origins

• The Coworking Space Saved My Life — The actual origin. A coworking space in Winchester, Virginia where a McDonald's dropout met generous strangers. The "for humans" philosophy was learned experientially before it was articulated technically.
• How I Develop Things and Why — The deeper principles: reduce cognitive load, match mental models, enhance agency, fail gracefully.
• Ahead of My Time, I Think — How this approach anticipated broader patterns in technology.
• A New Spin to Software Platform Design — Predicting app stores by thinking about how people actually find software.

Applied to Life

• Mental Health (for Humans) — The philosophy applied to psychiatry from ten years inside it. Diagnosis is a lookup key, not a life sentence. Treatment is the point.
• Breaking Changes — The DSM is versioned software, and nobody ships the humans a migration path.
• Entertaining the Brain, Effectively — Entertainment as cognitive service rather than attention exploitation.
• What Requests Taught Me About Marriage — Sensible defaults, graceful error handling, backwards compatibility. All relationship advice.
• Designing for the Worst Day — What "for humans" means when the human is having the worst day of their life.
• The Interface Is the Subconscious — Every interface shapes cognition before conscious awareness engages. Design accordingly.
• The Gift of Attention — Ethics of asking for consciousness in an attention economy.
• What Kids Taught Me About Creativity — Parenthood strips away tool fetishism to reveal what's actually sacred about making things.

Applied to Technology

• Programming as Spiritual Practice — When programming becomes conscious practice, every design choice becomes an ethical choice.
• The Recursive Loop: How Code Shapes Minds — The values we embody personally, we embed technologically.
• The Case for Bash — Sometimes the most human-centered choice is the boring, reliable tool that works everywhere.
• Version Control as Filesystem — Technical practices as contemplative practices.
• The Art of Naming Things in Code — Naming as the practice of creating shared meaning through careful attention to language.
• PyTheory: Breaking Through Five Years of Creative Block with AI — Music theory for humans. The same philosophy that drove Requests, applied to scales and chords.
• The Maintainer Is the Interface — The human behind the project is the first interface a contributor encounters. Design that accordingly.
• This Site Now Runs on Responder — Running on Responder: Requests semantics, server side. The "for humans" philosophy full circle.
• A Framework of One's Own — Why consuming and serving HTTP should share one mental model, and why a framework that fits one hand perfectly beats one that fits a market loosely.
• The Lego Bricks Era — The era when open source was about making beautiful lego bricks and sharing them.
• Visual Hierarchy and the Shape of Attention — How visual design directs consciousness before you realize it's happening.
• Python as English — The art of readable code as human-centered design at the syntax level.
• The Compiler in Your Head — How mental models shape what we build and what we can perceive.
• A Server Called Mercury — Deployment UX is critical infrastructure. What Heroku understood that the industry forgot.
• Infrastructure for One — Tools built for exactly one human: yourself. The economics finally allow it.
• RhymePad: Seeing the Sound — A tool that amplifies a craft instead of automating it away. The rhymes stay yours; the page just listens.

Applied to AI

• Building Rapport with Your AI — Context, trust, iteration. Same principles as human collaboration.
• Idea Amplification and Writing with AI — AI as accessibility device for neurodivergent minds.
• Obsidian Vaults & Claude Code — A CLAUDE.md at the vault root functions as an API contract. AI adapts to human thought patterns, not the other way around.
• Building a Digital Study Bible with AI — Technology serving contemplation.
• Temporal Code — AI systems that absorbed the psychology of programming, not just the syntax.
• How I Write Now — The "for humans" philosophy arriving at its own front door: AI as articulation prosthetic, and why access is the third category between slop and cheating.

The Dark Side: When Technology Doesn't Serve Humans

• The Algorithm Eats Virtue — The precise inversion of "for humans" design.
• The Algorithmic Mental Health Crisis — What happens when technology is designed to exploit rather than serve.
• The Metrics You Expose Are the Values You Endorse — Platform SDKs embed values. The metrics define what gets built.
• The Inclusion Illusion — Performative diversity that excludes the people who need accommodation most.
• The Internet Is a Net Negative — The honest reckoning.

This is probably the closest thing I have to a life philosophy, and it fits in a sentence: build things that respect the person using them. Everything else — the libraries, the essays, the consciousness research — is just working out the implications of that one idea across increasingly interesting domains.

Related Themes

• Open Source & Community — Community design as API design.
• Algorithmic Critique — What happens when these principles are violated at scale.
• Artificial Intelligence — Applying "for humans" to AI collaboration.
• Evolution of Ideas — How this principle evolved over fifteen years.