The DHH Problem  ## Metadata - Author: [[tomstu.art]] - Full Title: The DHH Problem - Category: #articles - Document Note: --- tags: - #dhh - #techculture - #rhetoric Author: tomstu.art Source: Personal website Reference: https://tomstu.art/the-dhh-problem date created: 2025-09-25 00:00 --- # Title: The DHH Problem — Context, Rhetoric, and Evolution ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: - Primary: “The DHH Problem” (2014 talk; updated note in 2020 acknowledging change in stance): https://tomstu.art/the-dhh-problem - Context: DHH is David Heinemeier Hansson, cofounder of Basecamp/HEY and creator of Ruby on Rails. ## 📝 Summary: The author reflects in 2020 on a 2014 talk criticizing DHH’s public conduct, noting that those criticisms no longer apply because DHH’s stance evolved toward advocating fairness, equality, privacy, and user needs. The author preserves the talk as a time-stamped snapshot rather than revising history. ## 📖 Main Content: - 2014: Critical talk about DHH’s rhetoric/behavior in tech. - 2020 update: Recognition of DHH’s growth and positive advocacy (fairness, equality, privacy, user-centricity). - Editorial choice: Keep the original talk online to preserve accountability and historical context rather than erase past views. ### 🗒️ Notes - Time context: - 2014: The original critique targeted then-current behaviors. - 2020: “Six years is a very long time on the internet”; behavior and advocacy changed. - Author stance: - Now broadly supportive of DHH’s current advocacy. - Avoids revisionism; opts for transparency by keeping the talk live. - Themes: - Personal and public evolution in tech leadership. - Accountability through archival transparency. - User-focused values: fairness, equality, privacy. ## 📖 References: - “The DHH Problem” (original talk, with 2020 update): https://tomstu.art/the-dhh-problem ## 🗣️ Paraphrase: 1) Original: “While I largely stand by my reasons for doing so… DHH has grown older and wiser… advocates for fairness, equality, privacy and the needs of users.” Paraphrase: I still understand why I delivered the critique back then, but DHH has matured and now champions equitable, privacy-conscious, user-first principles. 2) Original: “It would be weird to pretend I never said them… leaving the talk online as a snapshot of a particular moment in time.” Paraphrase: Erasing my past criticism would be disingenuous, so I’m keeping it published as a historical record of how views and people evolve. ## 📰 Newsletter: This week in learning web development: Beyond frameworks and features, leadership and rhetoric shape our ecosystem. A 2014 critique of DHH was recently revisited by its author, who now acknowledges DHH’s evolution toward fairness, equality, privacy, and user-first design. It’s a timely reminder that open-source communities grow when leaders—and critics—embrace transparency and change. Recent updates: explore modern CSS container queries, PHP 8+ performance wins, and accessibility testing with Playwright. Community highlights: new contributors shipping first patches on GitHub Discussions; shoutout to maintainers adopting Codespaces-based onboarding. Plugins to watch: performance profiling with Query Monitor, and security hardening via Wordfence. Keep learning, keep shipping, and remember: version control isn’t just for code—it’s for opinions too. Read the reflection: “The DHH Problem” (2014 talk; 2020 update acknowledging change): https://tomstu.art/the-dhh-problem ## ✅ Action Items: Prompt to align articles with your advocacy and OSPO goals: - For each article, analyze: - How the piece models transparent critique and historical accountability relevant to OSS governance. - Implications for contributor experience (onboarding, codes of conduct, communication norms). - Lessons for sustainable funding and user-centered priorities (fairness, privacy). - Educational opportunities: workshops or curricula that translate the article’s themes into practical skills (maintainer communication, conflict resolution, inclusive leadership). - OSPO alignment: policies for archival transparency, leader development, and community health metrics. - WordPress ecosystem fit: how these norms can improve contributor retention, mentorship pathways, and inclusive decision-making. - Output: - 3 takeaways for open-source advocacy. - 2 programmatic steps an OSPO could adopt. - 1 teaching artifact (lesson plan outline or lab). ## 🧪 Hypotheses: - H1: Maintaining public archives of critiques improves long-term community trust versus retracting or editing history. - H2: Visible evolution of influential leaders correlates with increased contributor retention. - H3: Public advocacy for fairness/privacy by leaders shifts community norms measurably (e.g., code of conduct adoption). ### 📊 Methodology: - Mixed-methods: - Quant: Compare contributor retention and PR velocity before/after leadership statements. - Qual: Interviews with maintainers/contributors about perceptions of trust and growth. - Content analysis: Sentiment/rhetorical analysis of leadership posts over time. - Data sources: GitHub API, project governance docs, mailing lists, social posts, archives. ### ❓ Questions: - How should communities balance accountability with recognition of growth? - What governance mechanisms best capture leader evolution without revisionism? - Do user-centered values by leaders measurably impact product decisions? ### 🔮 Future Research: - Longitudinal studies on rhetoric change among OSS leaders and downstream community health. - Best practices for preserving contentious historical content responsibly. - Metrics linking privacy-first advocacy to feature roadmaps. ### 💡 Implications: - Better evidence for OSPO policy on transparency. - Improved contributor onboarding grounded in trust. - Clearer guidance for leader communications training. ### 🧠 Learning Styles Assessment: - Readability: Likely upper high-school to early college (concise, reflective prose). - Visual: Minimal; add timeline infographic of stance evolution. - Aural: Provide audio narration or podcast discussion. - Verbal: Strong reflective language; could add linked readings on tech ethics. - Kinesthetic: Add actionable exercises (e.g., write your project’s “transparency policy”). - Logical: Introduce a framework for “critique lifecycle” with steps and criteria. - Social: Link to forums/Discussions for community debate. - Solitary: Add reflection prompts. - Naturalistic: Use real-world analogies about ecosystems adapting over time. ### 📊 Accessibility Assessment: - Ensure semantic headings (H1–H3). - Add alt-text for any images/timelines. - Verify keyboard navigability, sufficient contrast, responsive text resizing. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - Cultural relevance: Include examples across global OSS communities. - Inclusive language: Keep gender-neutral terms; define jargon. - Neurodiversity: Short paragraphs, lists, clear structure. - Representation: Feature diverse case studies and voices. - Psychological safety: Add content notes where critiques might be sensitive; encourage respectful dialogue. ### ✅ Logical validity: - Strengths: - Ethical reasoning: Acknowledges change and avoids revisionism, boosting credibility. - Balanced view: Holds past critique while recognizing growth. - Causal caution: Does not over-claim causality; frames as observation. - Weaknesses/Fallacies to avoid: - Hasty generalization: Don’t infer all leaders evolve similarly. - Appeal to authority: Avoid implying correctness solely b - Summary: Update (February 2020): I gave this talk almost six years ago. While I largely stand by my reasons for doing so, six years is a very long time on the internet. - URL: https://tomstu.art/the-dhh-problem Update (February 2020): I gave this talk almost [six years ago](http://2014.scottishrubyconference.com/). While I largely stand by my reasons for doing so, six years is a very long time on the internet. Since then DHH has grown older and wiser, and now uses his considerable influence to advocate for fairness, equality, privacy and the needs of users. He doesn’t need my approval — who the hell am I? — but, for the record, these days he has it. Although the things I said about 2014 DHH no longer apply to 2020 DHH, I think it would be weird to pretend I never said them, so I’m leaving the talk online as a snapshot of a particular moment in time. Update (April 2021): Uh, well, [this](https://janeyang.org/2021/04/27/an-open-letter-to-jason-and-david/) is [awkward](https://www.theverge.com/2021/4/27/22406673/basecamp-political-speech-policy-controversy). Apparently I was right the first time. We regret the error. Update (November 2022): [Sigh](https://world.hey.com/dhh/the-waning-days-of-dei-s-dominance-9a5b656c). I’m tired. A lightning talk from [Scottish Ruby Conference 2014](https://web.archive.org/web/http://lanyrd.com/2014/src2014/). Please contact me through [Twitter](http://twitter.com/tomstuart) or [email](mailto:[email protected]?subject=The%20DHH%20Problem) with any comments or corrections., The DHH Problem, tomstu.art, 01k600p5jn1w57rr85zhg6wce4.