💻 computer science

Writing Blog Posts Helps Students Connect Experiential Learning to the Workplace

This study demonstrates that requiring computer science students in work-based learning to write structured blog posts about their open source contributions facilitates deep reflection on technical challenges and growth, thereby helping them recognize and articulate the value of their experiences for future career opportunities.

Original authors: Utsab Saha, Lola Egherman, Ramiz Rahman, Mohd Toukir Khan, Kevin Wang, Tyler Menezes

Published 2026-04-22

📖 4 min read☕ Coffee break read

CC BY 4.0

Original authors: Utsab Saha, Lola Egherman, Ramiz Rahman, Mohd Toukir Khan, Kevin Wang, Tyler Menezes

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 you are a chef who just spent weeks perfecting a complex, multi-layered cake. You learned how to balance flavors, fix a broken oven, and manage a chaotic kitchen. But when you finally present the cake, you only see the tiny bit of frosting you added at the very end. You think, "I only did a little bit of work; this isn't impressive." So, you decide not to show the cake to anyone.

This is exactly what happens to many computer science students. They do incredible work in real-world projects, but they feel like they didn't do enough, so they hide their achievements.

This paper is about a simple trick to help students realize they are actually master chefs, not just frosting decorators.

The Problem: The "Imposter" Kitchen

In the world of coding, students often join programs where they fix bugs or add features to huge, popular software projects (like open-source projects). Their mentors (professional engineers) are usually blown away by the work.

However, the students feel different. Because they struggled with confusing code, spent hours fixing tiny formatting errors, or only changed a few lines of text, they feel like failures. They think, "I didn't write a whole new app; I just fixed a typo." Consequently, they leave these amazing stories off their resumes and don't talk about them in job interviews. They are hiding their best dishes.

The Solution: The "Storytelling Recipe Book"

To fix this, the researchers asked students to write a blog post on LinkedIn (a professional social network) about their project. But they didn't just say, "Write about what you did." They gave them a specific 5-step recipe (a template) to follow:

The Mission: What is this project? Who uses it? (The "Why")
The Problem: What specific thing were you trying to fix? (The "Challenge")
The Map: How does the software work? (The "Blueprint")
The Struggle: What went wrong? How did you try to fix it? (The "Drama")
The Fix: How did you solve it? (The "Victory")

Think of this like a travel journal. If you just say, "I went to Paris," it's boring. But if you write, "I got lost in the rain, asked a local for help, found a hidden bakery, and realized I love French bread," that's a story. The template forced students to stop looking at just the result (the code) and start looking at the journey (the learning).

What Happened When They Wrote?

The researchers read 25 of these blog posts and found four amazing things:

They became Detective Stories: Students realized they weren't just typing; they were solving mysteries. They described how they read manuals, asked for help, and tested ideas. They saw themselves as problem-solvers.
They Found Their "Growth Mindset": Many students wrote about the moment they finally understood something difficult. They realized, "I was stuck for three days, but then I figured it out." This turned their frustration into a badge of honor.
They Learned Teamwork: They talked about the messy reality of working with others—like when two people try to edit the same file and it breaks (a "merge conflict"). They learned that software is a team sport, not a solo act.
They Saw the Big Picture: Some realized their tiny fix helped thousands of people use the software better. They saw their small brick as part of a giant castle.

The Result: A New Identity

Before writing these posts, students saw themselves as "students who tried to code." After writing the posts, they started seeing themselves as "Engineers."

The survey results showed that by writing these stories, students gained a much clearer picture of their own skills. They could finally articulate why their work mattered. It was like giving them a mirror that showed their full potential instead of just their reflection in a funhouse mirror.

The Takeaway

The paper concludes that telling your story is just as important as doing the work.

In the same way a chef needs to explain the story of their dish to a diner, a developer needs to explain the story of their code to an employer. By using a simple, structured blog post, students can:

Stop feeling like imposters.
Realize that struggling is part of the job, not a failure.
Show off their skills to future bosses in a way that feels natural and professional.

In short: Don't just build the bridge; write a story about how you built it. That story is what will get you hired.

1. Problem Statement

Computer Science (CS) students participating in work-based learning (e.g., internships, open source contributions) often face a critical disconnect between their technical achievements and their self-perception.

The Phenomenon: Students frequently produce meaningful contributions (e.g., pull requests to major open source projects) that impress industry mentors. However, due to the difficulty of the process or the perception that their code changes were minimal, they view their work as a failure or insignificant.
The Consequence: This negative self-perception leads students to omit these valuable experiences from their resumes and job interviews, failing to signal their technical abilities to potential employers.
The Gap: There is a lack of structured mechanisms to help students re-contextualize their technical struggles and incremental progress into a professional narrative that highlights problem-solving skills and growth.

2. Methodology

The study employed a mixed-methods approach involving 25 junior and senior CS students from California and Washington who participated in the CodeDay Labs program (Fall 2024).

A. Intervention Design

Context: Students worked on real-world open source issues over 4–12 weeks, guided by industry mentors.
The Tool: Students were required to draft and publish a LinkedIn blog post using a specific 5-section structured template:
1. About the Project: Mission, importance, user scenarios, and screenshots.
2. The Issue: Specific problem addressed, codebase location, and artifacts.
3. Codebase Overview: Tech stack, system diagrams, and workflow walkthroughs.
4. Challenges: Specific technical hurdles, self-directed problem-solving attempts, and help-seeking behaviors.
5. Solution: Final implementation, testing/verification, and updated system diagrams.
Process: Students updated the blog weekly, aligning the sections with their current progress (e.g., learning the project in Week 1, facing challenges in Week 4).

B. Data Collection & Analysis

Qualitative (Thematic Analysis):
- Tool: ATLAS.ti software.
- Method: Two independent coders analyzed 25 blog posts using a coding reliability approach based on Braun and Clarke's framework.
- Metric: Inter-rater reliability was calculated using Cohen's Kappa ( $\kappa = 0.78$ ), indicating substantial agreement.
- Goal: Identify patterns in reflection topics and learning articulation.
Quantitative (Survey):
- Instrument: The Knowledge-Gain Survey by Mejia and Turns.
- Constructs: Measured reflection depth across four domains:
  1. Engineering Self (identity as an engineer).
  2. Course Understandings.
  3. Areas for Growth.
  4. Social Impact.
- Scale: 5-point Likert scale (normalized to 1–5).

3. Key Contributions

Structured Reflection Framework: The paper introduces and validates a specific 5-section blog post template designed to guide students from descriptive reporting to analytical reflection.
Professional Identity Development: It demonstrates how structured writing helps students construct a "professional narrative," transforming technical struggles into evidence of growth and problem-solving competence.
Low-Cost Scalability: The study proposes a scalable, low-cost intervention (blog writing) that can be integrated into capstones, micro-internships, and apprenticeships without requiring significant additional resources.

4. Results

A. Thematic Findings (RQ1: What do students reflect on?)

Four primary themes emerged from the blog posts:

Problem-Solving Techniques (96% of posts): Students explicitly articulated strategies such as reading documentation, debugging, narrowing down issues, and seeking peer/mentor help.
Growth Mindset (76% of posts): Students described the "click" moment where persistence led to understanding, reframing initial confusion as a learning opportunity.
Collaborative Development (56% of posts): Reflections covered both social aspects (communication with mentors/teams) and technical aspects (merge conflicts, code reviews).
User/Societal Impact (40% of posts): Students connected their code to broader user benefits, though this was the least frequent theme.

B. Quantitative Findings (RQ2: Depth of Reflection)

Using the Knowledge-Gain Survey, students demonstrated deep reflection across all four constructs:

Course Understandings: Highest mean score (4.34).
Areas for Growth: Mean score 4.17.
Engineering Self: Mean score 4.10.
Social Impact: Lowest mean score (3.72), suggesting students struggled to articulate the societal value of their specific code changes.

Note: Internal consistency (Cronbach's $\alpha$ ) was acceptable (> 0.70) for all constructs.

5. Significance and Implications

Bridging the Gap: The study confirms that structured blog writing effectively helps students recognize the value of their experiential learning, countering the tendency to dismiss difficult work as failure.
Hiring Signal: By articulating problem-solving techniques and growth mindsets, students generate a stronger signal of technical ability for employers than code metrics alone.
Limitations & Future Work:
- The study is descriptive with a small sample ( $n=25$ ) and lacks a control group.
- Students rarely reflected on "day-to-day" engineering realities (e.g., formatting, waiting for reviews), suggesting the template could be refined to prompt reflection on these mundane but critical professional skills.
- Future research should measure the actual impact of these posts on job acquisition rates.

Conclusion: Integrating structured reflective writing into CS experiential learning is a highly effective pedagogical strategy for fostering professional identity and helping students articulate the full value of their technical contributions.