A Critical Discourse Analysis of Gender Representation in Software Engineering Education Videos on YouTube
This study employs critical discourse analysis of 200 YouTube software engineering tutorials to reveal that male dominance in technical roles and the use of masculine linguistic defaults create a hidden curriculum that reinforces gendered norms and acts as a symbolic barrier to women's entry into the field.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine the internet as a giant, bustling library where millions of people go to learn how to build software. In this library, there are thousands of video tutorials on YouTube acting as the librarians. You might think these librarians are just handing out instruction manuals on how to write code, but this study suggests they are also handing out something invisible: a "hidden rulebook" about who belongs in the world of software engineering.
The researchers, Isabella Graßl, Alexander Serebrenik, and Giuseppe Destefanis, decided to peek behind the curtain. They didn't just count how many men and women appeared in the videos; they used a method called Critical Discourse Analysis. Think of this as a high-powered microscope that doesn't just look at the words on the page, but examines the tone, the pictures, and the unspoken messages to see what kind of reality the videos are building for the viewer.
Here is what they found, broken down into simple concepts:
1. The "Default" Setting is Male
The study looked at 200 videos (100 in English, 100 in German). They found that the "default setting" for a software engineer in these videos is almost always a man.
- The Name Game: When a video introduces a character to explain a concept (like a "Bank Manager" or a "System Admin"), that character is overwhelmingly named "Bob," "Thomas," or "Heini." In the German videos, for every single woman named, there were nearly five men. In English, it was better, but still skewed (almost two men for every one woman).
- The Pronoun Trap: In German, the language has a grammatical rule called the "generic masculine." It's like saying "The doctors are here" to mean all doctors, even if some are women. The study found that in German tutorials, this rule is used so heavily that it acts like a fog, making women invisible. Even when the video is about a generic user, the language defaults to "he." In English, creators tried harder to use neutral words like "they," but the bias was still there in other ways.
2. The "Action Hero" vs. The "Sidekick"
The researchers looked at Agency, which is a fancy word for "who gets to do the important stuff."
- The High-Agency Roles: These are the roles that make decisions, build the code, and solve the hard problems (like the Architect or the Lead Developer). In the videos, these roles were almost exclusively played by men.
- The Low-Agency Roles: These are the passive roles, like the "Customer," the "User," or the "Secretary." When women did appear in the videos, they were almost always stuck in these sidekick roles. They were the ones using the software, not the ones building it.
The Analogy: Imagine a cooking show. If the host is always a man chopping vegetables and seasoning the soup (the "builder"), and the only woman on screen is the one tasting the food or setting the table (the "user"), you start to believe that cooking is a man's job and eating is a woman's job. That is exactly what these software tutorials are doing.
3. The "Hidden Curriculum"
The paper argues that these videos have a Hidden Curriculum. This is like the unspoken rules you learn just by watching a show, rather than the official lesson plan.
- The Official Lesson: "Here is how you write a Java loop."
- The Hidden Lesson: "The person who writes Java loops is a man. The person who uses the app is a woman."
Even if the video creator doesn't intend to be sexist, the pattern of showing men as the experts and women as the consumers sends a powerful signal to female students: "This space isn't really for you."
4. English vs. German: A Tale of Two Languages
The study found a difference between the two languages, but the problem existed in both:
- German: The bias was very loud and obvious. The grammar itself (using "he" for everyone) combined with male names created a wall that was hard to climb.
- English: The bias was quieter. Creators used neutral words like "they" or "the user," which is good. However, the visuals and the roles still leaned heavily toward men. Even when they tried to be neutral, the "mental model" of the expert was still a guy.
5. Why This Matters
The researchers aren't saying these videos are "bad" tutorials. They are technically accurate. But they are like a map that only shows half the territory. If a young girl watches these videos and never sees a woman building the software, she might subconsciously decide that software engineering isn't her path.
The paper concludes that to fix this, we don't need to rewrite the code. We just need to rewrite the story. We need to see more women as the "Architects" and "Developers" in the examples, not just the "Customers." It's about making sure the invisible rulebook tells everyone, "You belong here," rather than just a specific group of people.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.