Essay proposes framework to evaluate authoritarianism in software development

The essay contends that authoritarian attitudes have become deeply embedded in the culture of software development, so that even programmers who oppose authority can act in authoritarian ways. This internalization occurs through shared norms, practices, and expectations that go unquestioned. The author argues that recognizing this hidden bias is the first step toward change. Without acknowledging it, efforts to improve processes may miss the root cause.

To address the issue, the essay proposes a concrete framework for evaluating software development practices, organizations, and communities. The framework looks for authoritarian and totalitarian policies and behaviors, such as forced conformity, suppression of dissent, and lack of opt-out mechanisms. It also separates the assessment of leaders from that of the broader community, allowing distinct diagnosis of where authoritarianism originates. This separation helps teams decide whether to change leadership, community norms, or both.

Adopting the framework requires engineers to invest time in examining their projects and to confront uncomfortable truths about power dynamics. It may lead to difficult conversations, potential conflict, or the decision to leave a project that fails the evaluation. The cost is therefore both analytical and interpersonal, but the author argues it prevents wasted effort in exploitative environments.

The framework is less useful when a project openly declares its authoritarian nature and participants give informed consent, because the criteria rely on hidden or non-consensual control. It also loses effectiveness if discussions fall into the fallacy of false equivalence, which obscures genuine authoritarian traits. In cases where informed consent is truly present, the essay suggests the system may not be authoritarian in the sense it aims to critique.