# Authoritarianism in Software Development: The Importance of Informed Consent

Understanding the impact of authoritarian structures in open source communities

- **Source:** [Hacker News: Front Page](https://brifing.si/source/b07aa772-b1a0-4a76-aa18-719c6f9e2dde)
- **Published:** 2026-08-23
- **Topic:** [Leadership](https://brifing.si/c/leadership)
- **Original article:** <https://zedshaw.com/blog/2020-10-07-authoritarianism-of-code/>
- **On Brifing:** https://brifing.si/s/b766766b-6ec0-4508-b27f-80b3735e6082

## Authoritarianism in the software world

Authoritarian behaviors have become so normalized in software development practices that even the most anti-authoritarian individuals participate in these systems. The 'Benevolent Dictator for Life' model is particularly common in open source projects. However, whether this model truly exists is debatable. Analyzing authoritarian structures in communities is crucial for participants to make informed choices about their involvement.

## The false equivalence trap

Programmers frequently fall prey to the 'False Equivalence' logical fallacy. When a new communication system is developed, critics might equate it with Twitter, regardless of actual differences. Yet these same individuals may claim their own projects are completely unique. This abstraction ability allows arbitrary redefinition of concepts, complicating analysis of authoritarian structures.

## The informed consent criterion

The key criterion for evaluating authoritarianism is whether participants gave 'informed consent.' Corporations or educational institutions may be authoritarian by nature, but participants join knowingly. The real problem occurs when authoritarian structures conceal this reality or misinform participants. Authority granted without informed consent forms the basis of authoritarian structures.

## Distinguishing leaders from communities

Analyzing authoritarianism requires separate evaluation of leaders and communities. Sometimes leaders behave correctly while the community becomes authoritarian, or vice versa. This distinction is critical for identifying problem sources and developing solutions. Participants who understand this dynamic can make more informed decisions about their involvement.

## Fascism vs. authoritarianism

Fascism should be viewed as a subset of authoritarianism. Using the term fascism often personalizes discussions and detracts from substantive analysis. The 'I'm not as bad as Hitler' defense is commonly used to justify authoritarian behavior. Authoritarianism encompasses any delegation or assumption of authority involving propaganda, coercion, or manipulation.

## Defining authoritarianism

Authoritarianism refers to any deference to authority given or taken without the enthusiastic informed consent of all involved. This definition covers not just leaders but authoritarian communities as well. Rather than focusing on specific behavior patterns or political ideologies, it emphasizes the fundamental lack of informed consent.

## Power dynamics in open source

Open source projects typically distribute power based on technical skill or contribution longevity. However, this system can gradually create hierarchical and authoritarian structures. The 'Benevolent Dictator' model may restrict participant input in some projects, particularly demotivating new contributors and limiting diverse perspectives.

## The role of community culture

A healthy community culture can counterbalance authoritarian tendencies. Environments where participants freely express ideas and participate in decision-making tend to be more sustainable. However, technical perfectionism or 'sacred project' mentalities can disrupt this balance. Community norms may normalize authoritarian behaviors over time.

## Psychological impacts of authoritarianism

Authoritarian structures can create psychological pressure on participants. Constant criticism, fear of exclusion, or 'real programmer' myths may damage self-confidence and hinder creativity. Marginalized groups often experience disproportionate impacts in such toxic environments. These dynamics ultimately harm collaboration and innovation.

## Alternative governance models

Meritocracy, direct democracy, or consensus-based decision making may reduce authoritarian tendencies, though each model presents challenges. Technical complexity can make equal participation practically difficult. The most effective systems often blend different approaches into hybrid models that balance various needs and perspectives.

## Steps toward change

Addressing authoritarian structures first requires acknowledging their existence. Initial steps might include establishing transparent communication channels, diversifying decision-making processes, and creating feedback mechanisms. Increasing community diversity helps incorporate different perspectives, though meaningful change requires time and sustained effort.

## The value of conscious participation

While contributing to software projects remains a personal choice, making that choice consciously is crucial. Participants should evaluate projects' governance structures, decision-making processes, and community cultures. Awareness of authoritarian structures helps individuals invest their time and energy more meaningfully, ultimately fostering healthier communities that produce more sustainable projects.

## Sources covering this story

- https://zedshaw.com/blog/2020-10-07-authoritarianism-of-code/ — 

---

_Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._
