[Paper] Folklore in Software Engineering: A Definition and Conceptual Foundations

Source: arXiv - 2601.21814v1

Overview

The paper “Folklore in Software Engineering: A Definition and Conceptual Foundations” investigates the stories, myths, jokes, and informal heuristics that circulate among software engineers—what the authors call software engineering folklore. By borrowing concepts from folklore studies, the authors aim to give developers a concrete vocabulary for the “unwritten rules” that shape daily work, team identity, and decision‑making.

Key Contributions

• Operational definition of software engineering folklore – informal, traditionally‑passed narratives and heuristics that influence how engineers think and act.
• Taxonomy of folklore artifacts (e.g., myths about “10x developers,” beliefs about where bugs hide, the notion of “technical debt”) classified by narrative form, symbolic meaning, and relevance to software‑engineering knowledge areas.
• Empirical grounding through a mixed‑method study: literature review + thematic analysis + semi‑structured interviews with 12 industry practitioners in Sweden.
• Insights into transmission mechanisms (storytelling, onboarding, code reviews, humor) and the dual role of folklore as a source of useful shortcuts and potential misconceptions.
• Research agenda linking folklore studies with software‑engineering ethnography and suggesting ways to make folklore a reflective practice tool.

Methodology

1. Literature Review & Thematic Analysis – Surveyed existing SE research, textbooks, blogs, and conference talks to collect recurring “folk” items; coded them for narrative structure, symbolic content, and occupational relevance.
2. Curated Folklore Corpus – Selected representative examples (e.g., “the 10‑hour rule for debugging,” “the myth of the perfect sprint”).
3. Semi‑Structured Interviews – Conducted with twelve software engineers from Swedish companies (startups to large enterprises) about how they encounter, share, and act upon such folklore.
4. Synthesis – Mapped interview excerpts onto the taxonomy, refining the definition and highlighting practical effects.

The approach is deliberately qualitative, focusing on depth of understanding rather than statistical generalization.

Results & Findings

• Folklore is pervasive: All interviewees reported hearing or using at least one piece of SE folklore, often without realizing it.
• Dual impact: Folklore can accelerate decision‑making (e.g., “if a bug appears after a merge, blame the integration step”) but also reinforce harmful stereotypes (e.g., the “10x developer” myth discourages collaboration).
• Transmission channels: Stories spread through informal chats, code‑review comments, onboarding sessions, and internal wikis. Humor serves as a “social glue” that makes the narratives memorable.
• Identity formation: Shared folklore helps teams develop a collective identity (“we’re the ‘bug‑hunters’”) and aligns values around quality, speed, or craftsmanship.
• Context‑sensitivity: Some folklore items are highly effective in certain environments (e.g., “run tests locally before committing” in CI‑heavy teams) but may be irrelevant or misleading elsewhere.

Practical Implications

• Onboarding & Mentoring: Deliberately surface useful folklore (e.g., “the rule of three for code duplication”) while flagging myths that hinder growth.
• Documentation & Knowledge Bases: Embed folklore explanations in internal wikis to preserve valuable heuristics that would otherwise be lost when senior engineers leave.
• Culture Audits: Use the taxonomy as a checklist to identify toxic myths (like the “hero‑coder” narrative) and replace them with evidence‑based practices.
• Tooling Opportunities: Linting or CI plugins could surface folklore‑related warnings (e.g., “Are you treating technical debt as a permanent feature?”) prompting reflection.
• Improved Communication: Recognizing that a joke about “the code‑base being alive” encodes a real risk (legacy entanglement) can lead to more precise risk discussions.

Limitations & Future Work

• Sample size & geography: Small interview pool (12 participants) limited to Sweden; may not capture cultural variations across regions or company sizes.
• Qualitative focus: Study provides rich insight but does not quantify performance impact of specific folklore items.
• Future directions: Large‑scale surveys to map folklore prevalence, longitudinal studies to track evolution with emerging practices (e.g., DevOps, AI‑assisted coding), and experimental interventions that replace harmful myths with data‑driven guidelines.

Authors

• Eduard Enoiu
• Jean Malm
• Gregory Gay

Paper Information

• arXiv ID: 2601.21814v1
• Categories: cs.SE
• Published: January 29, 2026
• PDF: Download PDF