Technical Summary: Folklore in Software Engineering

Problem Statement

Software Engineering (SE) is permeated by shared narratives, beliefs, jokes, customs, and myths that influence how professionals perceive their work, make decisions, and construct identities. While these cultural artifacts—ranging from historical anecdotes to persistent productivity myths—are widely recognized in practice, the field lacks a formal conceptual framework to define, analyze, or study them. Existing literature often dismisses these elements as anecdotal or unscientific, or attempts to "debunk" them as myths without understanding their cultural function. Consequently, there is a gap in understanding how informal knowledge, rituals, and narratives shape the socio-technical ecosystem of software development. This paper seeks to bridge that gap by applying theories from folklore studies to the occupational practices of software engineering.

Methodology

The research employs a multi-phase approach grounded in folklore theory and empirical investigation, as illustrated in the study's methodological framework:

1. Theoretical Grounding: The authors synthesized definitions and dimensions from folklore studies, specifically drawing on the work of Alan Dundes and Simon J. Bronner. They adapted concepts such as folk groups, informal transmission, tradition, rituals, myths, humor, and tacit knowledge to the SE context.
2. Literature Review and Item Curation: A manual search of SE literature (using Google Scholar and Google) identified publications addressing informal knowledge, belief systems, and narratives. Thirteen key publications were selected to extract exemplar folklore items (e.g., beliefs about defect locations, the "10x developer" legend, technical debt). These items were analyzed for their narrative form (myth, legend, anecdote, ritual, artifact), symbolic meaning (artifact, espoused value, or basic underlying assumption), associated occupational groups, and mapping to SE knowledge areas (via SWEBOK).
3. Interview Study: To ground these concepts in practice, the authors conducted semi-structured interviews with 12 industrial practitioners in Sweden. The participants represented diverse roles (developers, testers, managers, architects) and experience levels (9 to 41 years). The interviews explored participants' perceptions of folklore, specific examples of myths, rituals, and humor, and the mechanisms of transmission and impact.
4. Thematic Analysis: Data from the interviews were analyzed using Braun and Clarke's thematic analysis guidelines. Coding was performed iteratively and collaboratively by the authors to identify recurring patterns regarding the nature, manifestation, and transmission of SE folklore.

Key Contributions

The paper's primary contribution is the proposal of a working definition and conceptual foundation for Software Engineering Folklore.

• Definition: The authors define SE folklore as: "informally transmitted, traditional, and emergent narratives and heuristics enacted within occupational folk groups that shape identity, values, and collective knowledge."
• Conceptual Framework: The study categorizes folklore items into specific narrative forms (myths, legends, anecdotes, rituals, artifacts, humor) and analyzes their symbolic depth (ranging from visible artifacts to deep-seated underlying assumptions).
• Taxonomy of Manifestations: The paper identifies specific domains where folklore operates, including:
  • Myths and Beliefs: e.g., "Testing is a tedious burden," "Code is documentation," "AI will replace testers," and the "10x developer."
  • Rituals and Practices: e.g., stand-up meetings used for social bonding, specific naming conventions, and "tollgate" meetings that create a false sense of security.
  • Artifacts and Humor: e.g., office memes, jokes about "backlogs as graveyards," and physical clutter as a sign of professional identity.
  • Transmission Mechanisms: The study highlights how folklore is passed on through onboarding, informal mentorship, "hallway talk," coffee breaks, and community of practice interactions.

Results

The analysis of both the literature and the interview data revealed several critical insights:

• Folklore as Heuristic: Many folklore items function as heuristics that simplify reasoning in complex technical situations (e.g., "most defects are at interfaces"), even when they lack rigorous empirical grounding.
• Identity and Culture: Folklore is deeply tied to professional identity. Narratives about the "10x developer" or the "tedious nature of testing" reinforce specific role identities and hierarchies.
• Practice vs. Ideals: There is often a friction between formal processes (ideals) and the "lived" reality of work (practice). Folklore often fills the gap, offering workarounds or justifications for deviations from formal processes.
• Transmission and Persistence: Folklore persists through social reinforcement, storytelling, and ritual, often outlasting empirical evidence. Transmission is largely informal, occurring through mentorship, onboarding, and social interaction rather than formal documentation.
• Dual Nature: Practitioners view folklore as both helpful (providing context, workarounds, and social cohesion) and harmful (instilling unverified beliefs, creating resistance to change, or fostering blame cultures).

Significance and Claims

The authors position this work as a foundational step rather than a definitive solution. They argue that making the concept of SE folklore explicit provides a necessary basis for:

1. Future Ethnography and Folklore Studies: Establishing a vocabulary and framework for researchers to conduct deeper ethnographic investigations into the cultural dimensions of software engineering.
2. Reflective Practice: Enabling practitioners and managers to identify, reflect upon, and critically evaluate the narratives that shape their work. This allows teams to preserve context-effective heuristics while challenging unhelpful or unverified myths.
3. Bridging Theory and Practice: Connecting the abstract concepts of folklore studies with the concrete realities of software development, thereby offering a new lens to understand the human and cultural factors in technical work.

The paper modestly claims that its definition is a "working definition" intended to stimulate further investigation. It acknowledges limitations, such as the reliance on a purposive sample of experienced Swedish practitioners and the lack of longitudinal data, suggesting that future work is needed to validate these concepts across different demographics and organizational contexts.