<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Khushi Shah</title>
    <description>The latest articles on DEV Community by Khushi Shah (@khushishah_03).</description>
    <link>https://dev.to/khushishah_03</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4198360%2F19ee08a0-e06a-43ad-a487-a09d52d4271c.jpeg</url>
      <title>DEV Community: Khushi Shah</title>
      <link>https://dev.to/khushishah_03</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/khushishah_03"/>
    <language>en</language>
    <item>
      <title>Sorry, Wrong Number: A 5-Episode Microdrama Told Through Voice Notes</title>
      <dc:creator>Khushi Shah</dc:creator>
      <pubDate>Fri, 13 Nov 2026 10:29:26 +0000</pubDate>
      <link>https://dev.to/khushishah_03/sorry-wrong-number-a-5-episode-microdrama-told-through-voice-notes-3cc</link>
      <guid>https://dev.to/khushishah_03/sorry-wrong-number-a-5-episode-microdrama-told-through-voice-notes-3cc</guid>
      <description>&lt;p&gt;&lt;em&gt;A five-episode microdrama | Estimated reading time: 6 minutes&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;What if a wrong number brought the right people into each other's lives?&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Some conversations begin with a hello. Others begin with a mistake.&lt;/p&gt;

&lt;p&gt;Tara receives a voice note that was never meant for her. It was meant for someone named Kabir. At first, she thinks it is just a wrong number. But when more voice notes arrive, she discovers that the sender is carrying a story of loss, memories, and words that were never easy to say.&lt;/p&gt;

&lt;p&gt;What begins as an accidental exchange slowly becomes a connection between two strangers.&lt;/p&gt;

&lt;p&gt;This is &lt;strong&gt;Sorry, Wrong Number&lt;/strong&gt; — a five-episode microdrama told through voice notes.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Characters
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Tara:&lt;/strong&gt; A young woman who has not spoken to her mother for 47 days. She keeps postponing the call, even though she knows she wants to make it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Kabir:&lt;/strong&gt; The person the voice notes are meant for. He is no longer alive.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Sender:&lt;/strong&gt; Someone who continues sending voice notes meant for Kabir's mother, unaware that the number now belongs to Tara.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Episode 1: The Wrong Number
&lt;/h2&gt;

&lt;p&gt;Tara is scrolling through her phone when a voice note arrives from an unknown number.&lt;/p&gt;

&lt;p&gt;She plays it.&lt;/p&gt;

&lt;p&gt;The voice sounds emotional, almost as if the sender has been holding back tears.&lt;/p&gt;

&lt;p&gt;"Hi, Ma. I know I haven't called in a while. I just wanted to tell you something..."&lt;/p&gt;

&lt;p&gt;Tara pauses. The message clearly isn't meant for her.&lt;/p&gt;

&lt;p&gt;She types a reply:&lt;/p&gt;

&lt;p&gt;"Sorry, I think you have the wrong number."&lt;/p&gt;

&lt;p&gt;A few minutes later, another voice note arrives.&lt;/p&gt;

&lt;p&gt;This time, the sender says:&lt;/p&gt;

&lt;p&gt;"Is this not Kabir's number?"&lt;/p&gt;

&lt;p&gt;Tara looks at the screen.&lt;/p&gt;

&lt;p&gt;She doesn't know who Kabir is. But she can tell that this is more than an ordinary wrong-number situation.&lt;/p&gt;




&lt;h2&gt;
  
  
  Episode 2: The Voice Notes
&lt;/h2&gt;

&lt;p&gt;Tara decides to listen to the next voice note.&lt;/p&gt;

&lt;p&gt;The sender talks about small everyday things: a difficult day, a memory, and something they wish they could share with Kabir's mother.&lt;/p&gt;

&lt;p&gt;Tara finally replies:&lt;/p&gt;

&lt;p&gt;"I'm sorry, but I think you should know that this number belongs to someone else now."&lt;/p&gt;

&lt;p&gt;There is a long pause before the next message arrives.&lt;/p&gt;

&lt;p&gt;"Sorry. I didn't know. I used to send these messages here."&lt;/p&gt;

&lt;p&gt;Tara asks why.&lt;/p&gt;

&lt;p&gt;The answer changes the conversation.&lt;/p&gt;

&lt;p&gt;Kabir is no longer alive. The voice notes were meant for his mother, and sending them had become a way for the sender to keep those memories close.&lt;/p&gt;

&lt;p&gt;Tara doesn't know what to say.&lt;/p&gt;

&lt;p&gt;For once, she doesn't delete the conversation.&lt;/p&gt;




&lt;h2&gt;
  
  
  Episode 3: 47 Days
&lt;/h2&gt;

&lt;p&gt;As the messages continue, Tara and the sender begin talking—not just about Kabir, but about their own lives.&lt;/p&gt;

&lt;p&gt;Tara learns that sometimes a voice note is easier than a phone call. You can say things in your own time, without having to face the other person's immediate reaction.&lt;/p&gt;

&lt;p&gt;The conversation makes Tara think about her own mother.&lt;/p&gt;

&lt;p&gt;It has been &lt;strong&gt;47 days&lt;/strong&gt; since they last spoke.&lt;/p&gt;

&lt;p&gt;She opens her mother's contact, types a message, and deletes it. She tries again, but still cannot press send.&lt;/p&gt;

&lt;p&gt;The sender's words stay with her:&lt;/p&gt;

&lt;p&gt;"Sometimes, we keep waiting for the perfect moment to say something. But what if that moment never comes?"&lt;/p&gt;

&lt;p&gt;Tara looks at her mother's name on the screen.&lt;/p&gt;

&lt;p&gt;For the first time in 47 days, she considers making the call.&lt;/p&gt;




&lt;h2&gt;
  
  
  Episode 4: The Meeting
&lt;/h2&gt;

&lt;p&gt;After exchanging voice notes, Tara and the sender decide to meet at a metro station.&lt;/p&gt;

&lt;p&gt;They recognise each other from their conversations, but meeting face-to-face feels different.&lt;/p&gt;

&lt;p&gt;There is an awkward silence at first.&lt;/p&gt;

&lt;p&gt;Then they talk about Kabir, the messages, and how an accidental notification turned into something meaningful.&lt;/p&gt;

&lt;p&gt;Tara admits that she has been avoiding a conversation with her mother.&lt;/p&gt;

&lt;p&gt;The sender doesn't give her a dramatic speech or an easy solution. Instead, they remind her that sometimes the first step is simply saying hello.&lt;/p&gt;

&lt;p&gt;Before they part ways, Tara takes out her phone.&lt;/p&gt;

&lt;p&gt;She opens her mother's contact.&lt;/p&gt;

&lt;p&gt;This time, she doesn't close it.&lt;/p&gt;




&lt;h2&gt;
  
  
  Episode 5: The Right Person
&lt;/h2&gt;

&lt;p&gt;Tara finally calls her mother.&lt;/p&gt;

&lt;p&gt;The phone rings.&lt;/p&gt;

&lt;p&gt;Once.&lt;/p&gt;

&lt;p&gt;Twice.&lt;/p&gt;

&lt;p&gt;Then her mother answers.&lt;/p&gt;

&lt;p&gt;For a moment, Tara cannot find the words. But she doesn't hang up.&lt;/p&gt;

&lt;p&gt;"Ma..."&lt;/p&gt;

&lt;p&gt;That one word is enough to begin.&lt;/p&gt;

&lt;p&gt;Later, Tara receives one final voice note from the sender.&lt;/p&gt;

&lt;p&gt;"Thank you for listening. I know those messages were never meant for you. But somehow, you helped me feel like I wasn't speaking into silence."&lt;/p&gt;

&lt;p&gt;Tara smiles and replies:&lt;/p&gt;

&lt;p&gt;"Maybe it was a wrong number. But it reached the right person."&lt;/p&gt;

&lt;p&gt;The conversation ends.&lt;/p&gt;

&lt;p&gt;The screen fades.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sometimes, the wrong number leads you to the conversation you needed most.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Why I Chose This Format
&lt;/h2&gt;

&lt;p&gt;I wanted to experiment with a different kind of storytelling. Instead of depending on long descriptions and traditional narration, I wanted the audience to discover the characters through their voices.&lt;/p&gt;

&lt;p&gt;That's why I chose an &lt;strong&gt;audio-first storytelling format&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Here are five creative decisions that shaped the story:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;A simple but relatable hook:&lt;/strong&gt; A voice note arriving on the wrong phone is an everyday situation, but the mystery behind it makes the reader want to know more.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Storytelling through voices:&lt;/strong&gt; The characters reveal their emotions through voice notes, conversations, and pauses rather than lengthy explanations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Silence as an emotion:&lt;/strong&gt; Not every important moment needs dialogue. Sometimes an unanswered message or an unfinished sentence can communicate more than a paragraph.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Both characters have an emotional journey:&lt;/strong&gt; Tara learns to reconnect with her mother, while the sender finds a way to express memories and emotions that have been difficult to carry.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An ending that connects back to the beginning:&lt;/strong&gt; The wrong number starts the story, but by the end, it becomes a reminder that unexpected connections can sometimes bring the conversations we need most.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;My goal was to make readers feel as if they were listening to the characters rather than simply reading about them.&lt;/p&gt;




&lt;h2&gt;
  
  
  How I Used AI to Write This Story
&lt;/h2&gt;

&lt;p&gt;I wanted the story to feel natural and emotional, rather than like something generated from a single prompt. The creative process involved exploring the idea, thinking about the characters, and experimenting with how the story could unfold across five episodes.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Tools:&lt;/strong&gt; [Mention the AI tools actually used, such as ChatGPT or Claude.]&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;My process:&lt;/strong&gt; I started by developing the central idea and thinking about the emotional connection between the characters. I explored different ways to structure the five episodes and used AI tools to help organize the storyline, refine the wording, explore dialogue variations, and improve the pacing. I also reviewed the story to make sure each episode contributed something meaningful to the overall journey.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What worked:&lt;/strong&gt; AI helped me explore different approaches to the premise and organize the story into a clearer structure. It was useful for refining transitions, improving readability, and identifying places where the emotional moments could have a stronger impact.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What didn't:&lt;/strong&gt; Some initial versions felt too predictable and overly polished. The conversations sometimes sounded more like written dialogue than actual voice notes between people. I wanted the characters to sound natural, hesitant, and relatable. So I reworked the lines, simplified the conversations, and focused on making the emotions feel genuine rather than forced.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The biggest thing I learned was that writing an emotional story isn't just about what characters say. It's also about what they hesitate to say, what they leave unanswered, and what the reader understands without being told.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AI helped me explore and refine the story, but the emotional direction and final creative decisions came from my own vision.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Your Turn
&lt;/h2&gt;

&lt;p&gt;Which moment stayed with you the most?&lt;/p&gt;

&lt;p&gt;Was it Tara finally calling her mother, the unexpected voice notes, or the connection between two strangers who were never supposed to meet?&lt;/p&gt;

&lt;p&gt;And one question:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you received a voice note meant for someone else, would you simply reply "Wrong number" or would you listen to the story behind it?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I'd love to hear your thoughts in the comments.&lt;/p&gt;

&lt;p&gt;If enough readers are interested, maybe there is another story waiting to be told.&lt;/p&gt;




&lt;h2&gt;
  
  
  About Me
&lt;/h2&gt;

&lt;p&gt;I'm &lt;strong&gt;Khushi Shah&lt;/strong&gt;, a developer and writer from Pune, India.&lt;/p&gt;

&lt;p&gt;I enjoy building web applications, contributing to open source, exploring new technologies, and experimenting with creative storytelling.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/shahkhushi0307" rel="noopener noreferrer"&gt;shahkhushi0307&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;LinkedIn:&lt;/strong&gt; &lt;a href="https://www.linkedin.com/in/khushi-shah-31257b381/" rel="noopener noreferrer"&gt;Khushi Shah&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DEV Community:&lt;/strong&gt; &lt;a href="https://dev.to/khushishah_03"&gt;@khushishah_03&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instagram:&lt;/strong&gt; &lt;a href="https://www.instagram.com/_khushishah_03/" rel="noopener noreferrer"&gt;@_khushishah_03&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a work of fiction. All characters and events are fictional. Any resemblance to real persons or events is coincidental.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>fiction</category>
      <category>diversity</category>
      <category>writing</category>
      <category>podcast</category>
    </item>
    <item>
      <title>Beyond the First Commit: My Journey to Rank 48 at ECSoC’26</title>
      <dc:creator>Khushi Shah</dc:creator>
      <pubDate>Fri, 30 Oct 2026 12:05:39 +0000</pubDate>
      <link>https://dev.to/khushishah_03/beyond-the-first-commit-my-journey-to-rank-48-at-ecsoc26-256e</link>
      <guid>https://dev.to/khushishah_03/beyond-the-first-commit-my-journey-to-rank-48-at-ecsoc26-256e</guid>
      <description>&lt;p&gt;&lt;em&gt;From discovering open source to contributing 117 merged pull requests across 16 projects — a journey shaped by curiosity, collaboration, continuous learning, and consistency.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Khushi Shah&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
B.Tech Computer Science and Engineering at PW IOI&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Professional Profiles&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/shahkhushi0307" rel="noopener noreferrer"&gt;shahkhushi0307&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;LinkedIn:&lt;/strong&gt; &lt;a href="https://www.linkedin.com/in/khushi-shah-31257b381/" rel="noopener noreferrer"&gt;Khushi Shah&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instagram:&lt;/strong&gt; &lt;a href="https://www.instagram.com/_khushishah_03/" rel="noopener noreferrer"&gt;@_khushishah_03&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;ECSoC’26 Resources&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ecsoc-beta.vercel.app/profile/contributor/shahkhushi0307" rel="noopener noreferrer"&gt;Contributor Profile&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ecsoc-beta.vercel.app/leaderboard" rel="noopener noreferrer"&gt;Official Leaderboard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/drive/folders/1Npv1_jiCZpw2syRPEl-I4fBS-SANy_ta?usp=drive_link" rel="noopener noreferrer"&gt;Certificates and Supporting Documents&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;Open-source development offers something that traditional academic learning often cannot fully replicate: the opportunity to work on real-world software, collaborate with distributed developer communities, understand existing codebases, and contribute to projects used by others.&lt;/p&gt;

&lt;p&gt;My journey into this ecosystem began with curiosity and limited practical experience. I had an interest in software development, but I was still learning how collaborative development worked beyond individual projects and academic assignments.&lt;/p&gt;

&lt;p&gt;Participating in &lt;strong&gt;Elite Coder Summer of Code 2026 (ECSoC’26)&lt;/strong&gt; became an important turning point in that journey.&lt;/p&gt;

&lt;p&gt;By the conclusion of the program on August 31, 2026, I had achieved &lt;strong&gt;48th rank among approximately 13,000 participants and 822 active contributors&lt;/strong&gt;, with &lt;strong&gt;117 merged pull requests across 16 open-source projects&lt;/strong&gt; &lt;br&gt;
These achievements represent months of technical exploration, problem-solving, code reviews, collaboration, and consistent effort.&lt;/p&gt;

&lt;p&gt;However, the most meaningful part of this experience was not the final ranking. It was the transformation from someone unfamiliar with open-source contribution workflows into an active contributor capable of navigating multiple repositories and collaborating with project maintainers.&lt;/p&gt;

&lt;p&gt;This is the story behind that transformation.&lt;/p&gt;

&lt;h2&gt;
  
  
  01. The Foundation: My First Industry Experience
&lt;/h2&gt;

&lt;p&gt;I am a B.Tech Computer Science and Engineering student at PW IOI. My initial exposure to collaborative software development came through my first internship at &lt;strong&gt;PW LeapX as a Frontend Developer Intern&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The internship introduced me to practical development workflows and provided an opportunity to work in a team environment.&lt;/p&gt;

&lt;p&gt;Alongside frontend development, I gained experience with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Git and GitHub for version control and collaborative development.&lt;/li&gt;
&lt;li&gt;Working with team members on shared development tasks.&lt;/li&gt;
&lt;li&gt;Understanding project requirements and implementation workflows.&lt;/li&gt;
&lt;li&gt;Building and improving frontend interfaces.&lt;/li&gt;
&lt;li&gt;Participating in a structured software development environment.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This experience gave me a foundation for understanding how software is developed collaboratively.&lt;/p&gt;

&lt;p&gt;As I became more comfortable with GitHub, I started exploring public repositories and learning about open-source communities.&lt;/p&gt;

&lt;p&gt;I was particularly interested in the opportunity to contribute to existing software, learn from experienced developers, and understand how large projects evolve through community collaboration.&lt;/p&gt;

&lt;p&gt;At that stage, I was looking forward to participating in GSSoC. I had the motivation to contribute, but I still needed practical exposure to the open-source contribution process.&lt;/p&gt;

&lt;h2&gt;
  
  
  02. Discovering ECSoC’26: Taking the First Step
&lt;/h2&gt;

&lt;p&gt;My introduction to ECSoC’26 came through a friend who suggested that I register for &lt;strong&gt;Elite Coder Summer of Code 2026&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Initially, I was uncertain about participating.&lt;/p&gt;

&lt;p&gt;Although I had some development experience, I lacked a clear understanding of how open-source programs operated in practice. I was unfamiliar with repository selection, issue assignment, maintainer communication, contribution guidelines, and the pull request review process.&lt;/p&gt;

&lt;p&gt;I was interested in participating, but I questioned whether I had sufficient experience.&lt;/p&gt;

&lt;p&gt;A friend's encouragement helped me overcome that hesitation. Instead of waiting until I felt completely prepared, I decided to register and learn through the experience.&lt;/p&gt;

&lt;p&gt;That decision marked the beginning of my ECSoC’26 journey.&lt;/p&gt;

&lt;p&gt;The registration itself was straightforward. Understanding how to make meaningful contributions was the real challenge.&lt;/p&gt;

&lt;p&gt;I needed to learn how to identify suitable projects, understand their technical requirements, navigate unfamiliar codebases, and submit changes that met the expectations of maintainers.&lt;/p&gt;

&lt;h2&gt;
  
  
  03. Building Technical Understanding Through PW IOI
&lt;/h2&gt;

&lt;p&gt;An important part of my preparation came through an initiative introduced by &lt;strong&gt;PW IOI to encourage students to explore open-source development&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Through this initiative, I received guidance from &lt;strong&gt;Abhinav Awasthi Sir and Akash Meruva Sir&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Their mentorship helped me understand the practical aspects of contributing to open-source projects, including:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Exploring repositories and understanding their architecture.&lt;/li&gt;
&lt;li&gt;Reading documentation and contribution guidelines.&lt;/li&gt;
&lt;li&gt;Identifying issues suitable for contribution.&lt;/li&gt;
&lt;li&gt;Understanding GitHub workflows and pull request procedures.&lt;/li&gt;
&lt;li&gt;Communicating effectively with project maintainers.&lt;/li&gt;
&lt;li&gt;Incorporating review feedback and improving implementations.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This guidance helped me connect my existing development knowledge with the actual practices followed by open-source communities.&lt;/p&gt;

&lt;p&gt;I began approaching repositories more systematically, studying their structure, understanding the technologies they used, and identifying issues where I could make meaningful contributions.&lt;/p&gt;

&lt;p&gt;I am sincerely grateful to both mentors for their guidance and for helping me develop the confidence to begin contributing.&lt;/p&gt;

&lt;h2&gt;
  
  
  04. The First Merged Pull Request
&lt;/h2&gt;

&lt;p&gt;The transition from learning about open source to making an actual contribution was an important milestone.&lt;/p&gt;

&lt;p&gt;After exploring several repositories, I identified an issue that aligned with my technical understanding and expressed my interest in working on it.&lt;/p&gt;

&lt;p&gt;Once the issue was assigned, I began examining the relevant code, understanding the existing implementation, and identifying the changes required to address the problem.&lt;/p&gt;

&lt;p&gt;Like most first-time contributors, I had several concerns.&lt;/p&gt;

&lt;p&gt;Would my implementation satisfy the acceptance criteria? Had I understood the issue correctly? Would the maintainer approve the changes?&lt;/p&gt;

&lt;p&gt;Nevertheless, I completed the implementation and submitted my first pull request.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The pull request was merged the following day.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That first successful merge was a defining moment for me.&lt;/p&gt;

&lt;p&gt;It provided practical validation that I could contribute to an existing project, understand its requirements, and deliver changes that met the maintainer's expectations.&lt;/p&gt;

&lt;p&gt;More importantly, it changed how I viewed open-source development.&lt;/p&gt;

&lt;p&gt;I realised that contributing to an established project requires much more than writing code. It involves understanding context, respecting existing architecture, following development standards, communicating clearly, and responding constructively to feedback.&lt;/p&gt;

&lt;p&gt;My first merged pull request gave me the confidence to explore more repositories and take on increasingly challenging contributions.&lt;/p&gt;

&lt;h2&gt;
  
  
  05. Expanding My Contributions Across Projects
&lt;/h2&gt;

&lt;p&gt;Following my first successful contribution, I decided to remain actively involved throughout ECSoC’26.&lt;/p&gt;

&lt;p&gt;During July and August, I consistently explored new repositories, analysed open issues, worked on implementations, and submitted pull requests.&lt;/p&gt;

&lt;p&gt;Contributing across multiple projects exposed me to different codebases, development practices, technologies, and engineering approaches.&lt;/p&gt;

&lt;p&gt;Each repository presented a different learning opportunity.&lt;/p&gt;

&lt;p&gt;Some contributions required understanding unfamiliar project structures. Others involved debugging existing implementations, analysing requirements, or modifying code while maintaining compatibility with established functionality.&lt;/p&gt;

&lt;p&gt;The review process also became an important part of my learning.&lt;/p&gt;

&lt;p&gt;Maintainers frequently provided suggestions, requested refinements, or highlighted areas where implementations could be improved. Incorporating this feedback helped me develop a stronger understanding of code quality, maintainability, and collaborative engineering.&lt;/p&gt;

&lt;p&gt;Balancing contributions with academic responsibilities was another significant challenge.&lt;/p&gt;

&lt;p&gt;There were periods when managing college assignments and development work simultaneously required careful planning and discipline.&lt;/p&gt;

&lt;p&gt;Rather than focusing only on the number of contributions, I gradually developed a more consistent approach to learning and problem-solving.&lt;/p&gt;

&lt;p&gt;During this period, I also maintained a &lt;strong&gt;35-day GitHub contribution streak&lt;/strong&gt;, reflecting my commitment to making continuous progress.&lt;/p&gt;

&lt;h2&gt;
  
  
  06. ECSoC’26: Achievements and Milestones
&lt;/h2&gt;

&lt;p&gt;By August 31, 2026, my participation in ECSoC’26 had resulted in several milestones that I am proud to share.&lt;/p&gt;

&lt;h3&gt;
  
  
  Key achievements
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Achievement&lt;/th&gt;
&lt;th&gt;Result&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;ECSoC’26 Global Rank&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;48&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Merged Pull Requests&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;117&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Open-Source Projects&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;16&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GitHub Contribution Streak&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;35 days&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Total Program Participants&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Approximately 13,000&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Active Contributors&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;822&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Securing 48th rank was a significant achievement, but the numbers alone do not capture the complete experience.&lt;/p&gt;

&lt;p&gt;Each merged pull request represented an opportunity to understand a problem, analyse an existing implementation, develop a solution, and collaborate with maintainers.&lt;/p&gt;

&lt;p&gt;Contributing to 16 different projects strengthened my ability to adapt to unfamiliar codebases and work across different development environments.&lt;/p&gt;

&lt;p&gt;The experience also helped me become more independent in identifying problems, researching solutions, and implementing changes.&lt;/p&gt;

&lt;p&gt;Most importantly, it reinforced my understanding that technical growth comes through consistent practical engagement.&lt;/p&gt;

&lt;h2&gt;
  
  
  07. Recognition by PW IOI
&lt;/h2&gt;

&lt;p&gt;One of the most memorable highlights of this journey was having our ECSoC’26 achievement featured on the &lt;strong&gt;official PW IOI Instagram platform&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Being recognised by the institution's official platform was a meaningful moment, particularly because PW IOI had also played an important role in providing the learning environment and guidance that helped me begin my open-source journey.&lt;/p&gt;

&lt;p&gt;The recognition made the achievement even more special and highlighted the importance of encouraging students to participate in practical learning opportunities beyond the classroom.&lt;/p&gt;

&lt;p&gt;I am grateful to PW IOI for supporting initiatives that expose students to real-world development practices, technical communities, and opportunities for professional growth.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Official recognition:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.instagram.com/p/DfE_2I4k9qN/?img_index=1" rel="noopener noreferrer"&gt;View the ECSoC’26 Feature on PW IOI's Official Instagram&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.pwioi.com/" rel="noopener noreferrer"&gt;Visit the Official PW IOI Website&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  08. Technical and Professional Learnings
&lt;/h2&gt;

&lt;p&gt;Beyond the final ranking and contribution statistics, ECSoC’26 helped me develop several skills that will remain valuable throughout my software engineering journey.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Working with existing codebases&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I developed greater confidence in navigating unfamiliar repositories, understanding existing architecture, identifying dependencies, and making changes within established project structures.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Version control and collaborative workflows&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Regular contributions strengthened my understanding of Git, GitHub, branches, commits, pull requests, and collaborative development practices.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Code quality and maintainability&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Working with maintainers and responding to reviews helped me understand the importance of writing clean, readable, maintainable code that follows project conventions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Technical problem-solving&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Different issues required different approaches to debugging, research, implementation, and testing. This improved my ability to approach unfamiliar technical problems systematically.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Communication and collaboration&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Interacting with maintainers helped me understand how to communicate technical decisions, clarify requirements, discuss implementation approaches, and respond professionally to feedback.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Discipline and time management&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Maintaining regular contributions alongside academic responsibilities strengthened my ability to manage time and work consistently toward long-term goals.&lt;/p&gt;

&lt;p&gt;These experiences have helped me develop a more practical understanding of software engineering and collaborative development.&lt;/p&gt;

&lt;h2&gt;
  
  
  09. Advice for Students Beginning Their Open-Source Journey
&lt;/h2&gt;

&lt;p&gt;For students who are interested in open source but are unsure about where to begin, my biggest recommendation is to start with what you already know and build from there.&lt;/p&gt;

&lt;p&gt;You do not need to master every technology or understand every aspect of software engineering before making your first contribution.&lt;/p&gt;

&lt;p&gt;Start by becoming comfortable with Git and GitHub. Explore repositories that interest you, read their documentation, understand their contribution guidelines, and identify issues that match your current skill level.&lt;/p&gt;

&lt;p&gt;Do not hesitate to ask maintainers for clarification when necessary.&lt;/p&gt;

&lt;p&gt;Your first contribution may require several attempts. Your pull request might receive review comments, and your implementation may need modifications before it is accepted.&lt;/p&gt;

&lt;p&gt;These are normal parts of collaborative software development.&lt;/p&gt;

&lt;p&gt;Instead of viewing feedback as rejection, treat it as an opportunity to improve your technical understanding.&lt;/p&gt;

&lt;p&gt;Most importantly, focus on learning rather than comparing your progress with someone else's achievements.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You do not have to be an expert to contribute to open source. You have to be willing to learn, collaborate, and improve with every contribution.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  10. Acknowledgements
&lt;/h2&gt;

&lt;p&gt;This journey has been shaped by the support, encouragement, and guidance of several individuals and communities.&lt;/p&gt;

&lt;p&gt;I would like to express my sincere gratitude to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;My friend&lt;/strong&gt;, whose encouragement motivated me to register for ECSoC’26 when I was initially hesitant.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PW LeapX&lt;/strong&gt;, for providing my first internship experience and introducing me to collaborative software development.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PW IOI&lt;/strong&gt;, for creating valuable learning opportunities and encouraging students to participate in open-source initiatives.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Abhinav Awasthi Sir and Akash Meruva Sir&lt;/strong&gt;, for their mentorship, guidance, and support in helping me understand the open-source contribution process.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open-source maintainers and developer communities&lt;/strong&gt;, for reviewing my contributions, sharing constructive feedback, and providing an environment for continuous learning.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I am thankful to everyone who contributed to this experience and helped make it a memorable milestone in my journey.&lt;/p&gt;

&lt;h2&gt;
  
  
  Looking Forward
&lt;/h2&gt;

&lt;p&gt;ECSoC’26 has been an important milestone in my development journey, but I consider it a foundation for what comes next.&lt;/p&gt;

&lt;p&gt;The experience has strengthened my interest in open-source software development and encouraged me to continue contributing to meaningful projects, exploring new technologies, and collaborating with developers across different communities.&lt;/p&gt;

&lt;p&gt;From being uncertain about my first contribution to achieving 48th rank, this journey has reinforced an important lesson: progress begins when we are willing to step beyond our comfort zone and learn through experience.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;117 merged pull requests. 16 open-source projects. A 35-day contribution streak. One transformative learning experience.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;These milestones represent not only what I accomplished during ECSoC’26, but also the skills, confidence, and perspective I gained along the way.&lt;/p&gt;

&lt;p&gt;I look forward to building on this experience, taking on new challenges, and contributing to the open-source ecosystem in the future.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The journey continues.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Connect With Me
&lt;/h2&gt;

&lt;p&gt;I welcome opportunities to connect with developers, open-source contributors, technology enthusiasts, and communities working on meaningful projects.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/shahkhushi0307" rel="noopener noreferrer"&gt;github.com/shahkhushi0307&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;LinkedIn:&lt;/strong&gt; &lt;a href="https://www.linkedin.com/in/khushi-shah-31257b381/" rel="noopener noreferrer"&gt;Khushi Shah&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instagram:&lt;/strong&gt; &lt;a href="https://www.instagram.com/_khushishah_03/" rel="noopener noreferrer"&gt;@_khushishah_03&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  ECSoC’26 Achievement Resources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ecsoc-beta.vercel.app/profile/contributor/shahkhushi0307" rel="noopener noreferrer"&gt;ECSoC’26 Contributor Profile&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ecsoc-beta.vercel.app/leaderboard" rel="noopener noreferrer"&gt;ECSoC’26 Official Leaderboard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/drive/folders/1Npv1_jiCZpw2syRPEl-I4fBS-SANy_ta?usp=drive_link" rel="noopener noreferrer"&gt;Certificates and Supporting Documents&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.instagram.com/p/DfE_2I4k9qN/?img_index=1" rel="noopener noreferrer"&gt;PW IOI Official Instagram Feature&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>opensource</category>
      <category>github</category>
    </item>
    <item>
      <title>Learning to Building: My Journey as a Full Stack Developer Intern at PW LeapX</title>
      <dc:creator>Khushi Shah</dc:creator>
      <pubDate>Fri, 30 Oct 2026 11:34:27 +0000</pubDate>
      <link>https://dev.to/khushishah_03/learning-to-building-my-journey-as-a-full-stack-developer-intern-at-pw-leapx-5d6j</link>
      <guid>https://dev.to/khushishah_03/learning-to-building-my-journey-as-a-full-stack-developer-intern-at-pw-leapx-5d6j</guid>
      <description>&lt;p&gt;·&lt;br&gt;
Reflections on my Full Stack Developer internship at PW LeapX, working on ClassForge, exploring modern web technologies, and learning real-world software engineering practices.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;By Khushi Shah· BTech at Computer Science Student at PW IOI Pune&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;There is a significant difference between learning software development and experiencing how software is actually built.&lt;/p&gt;

&lt;p&gt;As students, much of our early development journey revolves around programming languages, technical concepts, coding assignments, tutorials, and personal projects. We learn how to write code, solve problems, and build functional interfaces. However, understanding how these individual skills come together to create a real-world product requires an entirely different perspective.&lt;/p&gt;

&lt;p&gt;Questions such as &lt;em&gt;How does an idea become a working product? How do development teams collaborate? What goes into building scalable applications?&lt;/em&gt; were things I wanted to understand beyond the classroom.&lt;/p&gt;

&lt;p&gt;My journey as a &lt;strong&gt;Full Stack Developer Intern at PW LeapX&lt;/strong&gt; gave me the opportunity to explore these questions firsthand.&lt;/p&gt;

&lt;p&gt;What began as an opportunity to apply my technical knowledge gradually evolved into a meaningful learning experience, helping me understand the practical aspects of software development, teamwork, product thinking, and engineering practices.&lt;/p&gt;

&lt;p&gt;Here is a reflection on my experience so far.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The Transition from Learning to Practical Development
&lt;/h2&gt;

&lt;p&gt;Understanding programming concepts and implementing them in real-world applications are two different experiences.&lt;/p&gt;

&lt;p&gt;While academic assignments generally come with well-defined requirements and expected outputs, real-world development involves understanding the problem before deciding on the solution.&lt;/p&gt;

&lt;p&gt;It requires considering multiple aspects, including:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Understanding functional and technical requirements.&lt;/li&gt;
&lt;li&gt;Designing maintainable application architectures.&lt;/li&gt;
&lt;li&gt;Building intuitive and responsive user interfaces.&lt;/li&gt;
&lt;li&gt;Managing application data and state.&lt;/li&gt;
&lt;li&gt;Integrating frontend components with backend services.&lt;/li&gt;
&lt;li&gt;Ensuring consistency across different modules.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I wanted to experience this complete development process rather than limit my learning to individual technologies or isolated projects.&lt;/p&gt;

&lt;p&gt;Joining PW LeapX provided an opportunity to take that step.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Getting Started at PW LeapX
&lt;/h2&gt;

&lt;p&gt;Getting selected as a &lt;strong&gt;Full Stack Developer Intern at PW LeapX&lt;/strong&gt; was an important milestone in my development journey.&lt;/p&gt;

&lt;p&gt;It introduced me to a collaborative engineering environment where understanding the project, exploring existing implementations, and coordinating with team members were just as important as writing code.&lt;/p&gt;

&lt;p&gt;One of my earliest realizations was that software development does not begin with opening a code editor.&lt;/p&gt;

&lt;p&gt;It begins with understanding the problem.&lt;/p&gt;

&lt;p&gt;Before implementing a feature, developers need to understand its purpose, existing application structure, dependencies, and expected behaviour. Reading requirements, exploring the codebase, discussing implementation approaches, and breaking down tasks are essential parts of the process.&lt;/p&gt;

&lt;p&gt;This experience also helped me appreciate the importance of communication and collaboration when multiple developers contribute to the same product.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Working on ClassForge: A Multi-Tenant School Management Platform
&lt;/h2&gt;

&lt;p&gt;One of the major projects I have been contributing to at PW LeapX is &lt;strong&gt;ClassForge&lt;/strong&gt;, a multi-tenant School Management System designed to bring various academic and administrative operations together on a unified platform.&lt;/p&gt;

&lt;p&gt;The platform aims to provide dedicated experiences for different user roles, including school administrators, teachers, and students.&lt;/p&gt;

&lt;p&gt;What makes ClassForge particularly interesting is the coordination required between different modules, permissions, user roles, and application workflows.&lt;/p&gt;

&lt;p&gt;My contributions and learning have involved several areas of the application:&lt;/p&gt;

&lt;h3&gt;
  
  
  Authentication and Login Experience
&lt;/h3&gt;

&lt;p&gt;Working on the login interface and understanding how frontend authentication flows connect with backend authentication services and user information.&lt;/p&gt;

&lt;h3&gt;
  
  
  Dashboard Development
&lt;/h3&gt;

&lt;p&gt;Contributing to structured dashboard interfaces that present relevant information and help users navigate different sections of the application.&lt;/p&gt;

&lt;h3&gt;
  
  
  School Management and Settings
&lt;/h3&gt;

&lt;p&gt;Working on school workspace experiences and settings interfaces for managing school-related configurations and administrative information.&lt;/p&gt;

&lt;h3&gt;
  
  
  Frontend Development
&lt;/h3&gt;

&lt;p&gt;Translating design requirements into functional interfaces using reusable components, maintaining consistent layouts, and ensuring responsive behaviour across screen sizes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Frontend-Backend Integration
&lt;/h3&gt;

&lt;p&gt;Understanding how frontend components communicate with backend APIs, how application data flows between different layers, and how authentication and database operations contribute to the overall system.&lt;/p&gt;

&lt;p&gt;Working on ClassForge has reinforced an important engineering principle: building a product is not simply about creating individual screens. It is about making sure every component and module works together as part of a consistent, reliable application.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Technologies and Engineering Concepts
&lt;/h2&gt;

&lt;p&gt;Working on ClassForge has given me the opportunity to explore how different technologies work together within a modern web application.&lt;/p&gt;

&lt;p&gt;Some of the technologies I have been working with and strengthening my understanding of include:&lt;/p&gt;

&lt;h3&gt;
  
  
  React
&lt;/h3&gt;

&lt;p&gt;Developing a better understanding of component-based architecture, reusable UI elements, state management, and building interactive user interfaces.&lt;/p&gt;

&lt;h3&gt;
  
  
  Next.js
&lt;/h3&gt;

&lt;p&gt;Exploring application routing, modern rendering capabilities, and structuring frontend and backend functionality within a unified application framework.&lt;/p&gt;

&lt;h3&gt;
  
  
  TypeScript
&lt;/h3&gt;

&lt;p&gt;Understanding the importance of static typing, predictable data structures, and maintainability when working with larger codebases.&lt;/p&gt;

&lt;h3&gt;
  
  
  PostgreSQL
&lt;/h3&gt;

&lt;p&gt;Strengthening my understanding of relational databases, data modelling, relationships, and how application data is stored and retrieved.&lt;/p&gt;

&lt;p&gt;Beyond learning these technologies individually, the most valuable part has been understanding how they interact.&lt;/p&gt;

&lt;p&gt;For example, a user interaction on the frontend may trigger an API request, which communicates with the backend, performs the required database operation, and returns a response that the interface needs to handle appropriately.&lt;/p&gt;

&lt;p&gt;Understanding this complete flow has helped me develop a broader perspective on full-stack development.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Understanding Existing Codebases and Team Workflows
&lt;/h2&gt;

&lt;p&gt;One of the most valuable lessons from this experience has been realizing that software development involves much more than writing new code.&lt;/p&gt;

&lt;p&gt;A significant part of working on an existing product is understanding the code that is already there.&lt;/p&gt;

&lt;p&gt;When contributing to an established codebase, it is important to understand its folder structure, component relationships, existing implementation patterns, dependencies, and architectural decisions before making changes.&lt;/p&gt;

&lt;p&gt;Sometimes, a seemingly small feature requires understanding multiple interconnected modules.&lt;/p&gt;

&lt;p&gt;This has helped me appreciate the importance of:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Writing clean and readable code.&lt;/li&gt;
&lt;li&gt;Building reusable and maintainable components.&lt;/li&gt;
&lt;li&gt;Following consistent naming conventions.&lt;/li&gt;
&lt;li&gt;Understanding existing implementation patterns.&lt;/li&gt;
&lt;li&gt;Using Git and GitHub effectively.&lt;/li&gt;
&lt;li&gt;Communicating changes and collaborating with teammates.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These practices are not merely technical preferences. They form the foundation of effective software engineering, particularly when working on products developed by multiple contributors.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Developing a Product-Oriented Approach to UI/UX
&lt;/h2&gt;

&lt;p&gt;Coming from an interest in frontend development, one of the interesting aspects of this internship has been learning to look beyond the visual appearance of an interface.&lt;/p&gt;

&lt;p&gt;A good user interface is not defined only by colours, typography, spacing, or visual elements.&lt;/p&gt;

&lt;p&gt;It is defined by how effectively users can interact with the application.&lt;/p&gt;

&lt;p&gt;While working on different interfaces, I have started considering questions such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Is the navigation intuitive?&lt;/li&gt;
&lt;li&gt;Is information presented in a logical structure?&lt;/li&gt;
&lt;li&gt;Are similar components consistent throughout the application?&lt;/li&gt;
&lt;li&gt;How does the interface behave when data is unavailable?&lt;/li&gt;
&lt;li&gt;Is the experience responsive across different devices?&lt;/li&gt;
&lt;li&gt;Does the interface communicate loading, success, and error states clearly?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These considerations have helped me understand the practical relationship between UI design, user experience, and frontend engineering.&lt;/p&gt;

&lt;p&gt;The goal is not simply to build an interface that looks good, but to create one that is understandable, accessible, and functional.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Key Lessons and Takeaways
&lt;/h2&gt;

&lt;p&gt;Looking back at my experience so far, a few lessons stand out.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Understand the Requirement Before Writing Code
&lt;/h3&gt;

&lt;p&gt;A clear understanding of the problem and existing architecture helps prevent unnecessary rework and leads to better implementation decisions.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Write Code for Maintainability, Not Just Functionality
&lt;/h3&gt;

&lt;p&gt;Code should be understandable, reusable, and easy for other developers to work with.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Communication Is an Essential Engineering Skill
&lt;/h3&gt;

&lt;p&gt;Discussing implementation approaches, asking questions, sharing progress, and communicating blockers are important parts of collaborative development.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Understand the Complete Application Flow
&lt;/h3&gt;

&lt;p&gt;Knowing how the frontend, backend, APIs, authentication, and databases interact provides a much stronger understanding of how modern applications work.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Treat Challenges as Learning Opportunities
&lt;/h3&gt;

&lt;p&gt;Unfamiliar code, unexpected bugs, and new concepts are inevitable. Approaching them with curiosity and patience is essential for continuous improvement.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Beyond the Internship: A Shift in Perspective
&lt;/h2&gt;

&lt;p&gt;The biggest outcome of this experience is not simply the number of technologies I have explored or the features I have contributed to.&lt;/p&gt;

&lt;p&gt;It is the change in how I approach software development.&lt;/p&gt;

&lt;p&gt;Earlier, my primary focus was often on completing a coding task or implementing a particular feature.&lt;/p&gt;

&lt;p&gt;Now, I find myself thinking about broader engineering questions:&lt;/p&gt;

&lt;p&gt;Why is this feature needed? How does it fit into the existing architecture? How will users interact with it? What happens when something goes wrong? Can the implementation be maintained and extended in the future?&lt;/p&gt;

&lt;p&gt;This shift from task-oriented development to product-oriented thinking is something I consider one of the most valuable outcomes of my internship.&lt;/p&gt;

&lt;p&gt;I am grateful to &lt;strong&gt;PW LeapX&lt;/strong&gt; for providing me with this opportunity, to my mentors for their guidance, and to my teammates for creating an environment where collaboration and continuous learning are encouraged.&lt;/p&gt;

&lt;p&gt;Every implementation, discussion, challenge, and bug has contributed something valuable to my learning journey.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. A Message to Aspiring Developers
&lt;/h2&gt;

&lt;p&gt;For students who are learning software development and waiting for the right opportunity to work on real-world applications, I would like to share one simple thought:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do not wait until you know everything to start building.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Work on projects. Explore unfamiliar technologies. Learn Git and GitHub. Read existing codebases. Collaborate with other developers. Most importantly, understand the reasoning behind the code you write.&lt;/p&gt;

&lt;p&gt;You do not need to have all the answers before taking your first step. What matters is your willingness to learn, experiment, accept feedback, and improve consistently.&lt;/p&gt;

&lt;p&gt;I am still learning, exploring new technologies, and discovering better ways to approach engineering challenges. However, this experience at PW LeapX has given me a much clearer understanding of what it means to contribute to a real-world software product.&lt;/p&gt;

&lt;p&gt;From understanding concepts in the classroom to applying them in a collaborative development environment, this journey has been an important step in my growth as a developer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;And this is only the beginning. 🚀&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Let's Connect and Grow Together
&lt;/h2&gt;

&lt;p&gt;I believe that continuous learning, collaboration, and sharing experiences play an important role in becoming a better developer.&lt;/p&gt;

&lt;p&gt;I'm always excited to connect with fellow developers, explore new technologies, exchange ideas, and learn from the experiences of others.&lt;/p&gt;

&lt;p&gt;If you're interested in technology, software development, or building meaningful products, feel free to connect with me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/shahkhushi0307" rel="noopener noreferrer"&gt;shahkhushi0307&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;LinkedIn:&lt;/strong&gt; &lt;a href="https://www.linkedin.com/in/khushi-shah-31257b381/" rel="noopener noreferrer"&gt;Khushi Shah&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instagram:&lt;/strong&gt; &lt;a href="https://www.instagram.com/_khushishah_03/" rel="noopener noreferrer"&gt;@_khushishah_03&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Thank you for taking the time to read about my journey at PW LeapX.&lt;/p&gt;

&lt;p&gt;I'm looking forward to continuing this journey of learning, building, contributing, and growing as a developer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Every opportunity to learn is an opportunity to build something better.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This is just the beginning!&lt;/em&gt;&lt;/p&gt;




</description>
      <category>github</category>
      <category>internship</category>
      <category>webdev</category>
      <category>fullstack</category>
    </item>
    <item>
      <title>Beyond the First Commit: My Journey to Rank 48 at ECSoC’26</title>
      <dc:creator>Khushi Shah</dc:creator>
      <pubDate>Fri, 30 Oct 2026 11:21:38 +0000</pubDate>
      <link>https://dev.to/khushishah_03/beyond-the-first-commit-my-journey-to-rank-46-at-ecsoc26-4hpp</link>
      <guid>https://dev.to/khushishah_03/beyond-the-first-commit-my-journey-to-rank-46-at-ecsoc26-4hpp</guid>
      <description>&lt;h1&gt;
  
  
  Beyond the First Commit: My Journey to Rank 46 at ECSoC’26
&lt;/h1&gt;

&lt;p&gt;&lt;em&gt;From discovering open source to contributing 117 merged pull requests across 16 projects — a journey shaped by curiosity, collaboration, continuous learning, and consistency.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Khushi Shah&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
B.Tech Computer Science and Engineering | PW IOI&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Professional Profiles&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/shahkhushi0307" rel="noopener noreferrer"&gt;shahkhushi0307&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;LinkedIn:&lt;/strong&gt; &lt;a href="https://www.linkedin.com/in/khushi-shah-31257b381/" rel="noopener noreferrer"&gt;Khushi Shah&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instagram:&lt;/strong&gt; &lt;a href="https://www.instagram.com/_khushishah_03/" rel="noopener noreferrer"&gt;@_khushishah_03&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;ECSoC’26 Resources&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ecsoc-beta.vercel.app/profile/contributor/shahkhushi0307" rel="noopener noreferrer"&gt;Contributor Profile&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ecsoc-beta.vercel.app/leaderboard" rel="noopener noreferrer"&gt;Official Leaderboard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/drive/folders/1Npv1_jiCZpw2syRPEl-I4fBS-SANy_ta?usp=drive_link" rel="noopener noreferrer"&gt;Certificates and Supporting Documents&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;Open-source development offers something that traditional academic learning often cannot fully replicate: the opportunity to work on real-world software, collaborate with distributed developer communities, understand existing codebases, and contribute to projects used by others.&lt;/p&gt;

&lt;p&gt;My journey into this ecosystem began with curiosity and limited practical experience. I had an interest in software development, but I was still learning how collaborative development worked beyond individual projects and academic assignments.&lt;/p&gt;

&lt;p&gt;Participating in &lt;strong&gt;Elite Coder Summer of Code 2026 (ECSoC’26)&lt;/strong&gt; became an important turning point in that journey.&lt;/p&gt;

&lt;p&gt;By the conclusion of the program on August 31, 2026, I had achieved &lt;strong&gt;48th rank among approximately 13,000 participants and 822 active contributors&lt;/strong&gt;, with &lt;strong&gt;117 merged pull requests across 16 open-source projects&lt;/strong&gt; and a &lt;strong&gt;35-day GitHub contribution streak&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;These achievements represent months of technical exploration, problem-solving, code reviews, collaboration, and consistent effort.&lt;/p&gt;

&lt;p&gt;However, the most meaningful part of this experience was not the final ranking. It was the transformation from someone unfamiliar with open-source contribution workflows into an active contributor capable of navigating multiple repositories and collaborating with project maintainers.&lt;/p&gt;

&lt;p&gt;This is the story behind that transformation.&lt;/p&gt;

&lt;h2&gt;
  
  
  01. The Foundation: My First Industry Experience
&lt;/h2&gt;

&lt;p&gt;I am a B.Tech Computer Science and Engineering student at PW IOI. My initial exposure to collaborative software development came through my first internship at &lt;strong&gt;PW LeapX as a Frontend Developer Intern&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The internship introduced me to practical development workflows and provided an opportunity to work in a team environment.&lt;/p&gt;

&lt;p&gt;Alongside frontend development, I gained experience with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Git and GitHub for version control and collaborative development.&lt;/li&gt;
&lt;li&gt;Working with team members on shared development tasks.&lt;/li&gt;
&lt;li&gt;Understanding project requirements and implementation workflows.&lt;/li&gt;
&lt;li&gt;Building and improving frontend interfaces.&lt;/li&gt;
&lt;li&gt;Participating in a structured software development environment.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This experience gave me a foundation for understanding how software is developed collaboratively.&lt;/p&gt;

&lt;p&gt;As I became more comfortable with GitHub, I started exploring public repositories and learning about open-source communities.&lt;/p&gt;

&lt;p&gt;I was particularly interested in the opportunity to contribute to existing software, learn from experienced developers, and understand how large projects evolve through community collaboration.&lt;/p&gt;

&lt;p&gt;At that stage, I was looking forward to participating in GSSoC. I had the motivation to contribute, but I still needed practical exposure to the open-source contribution process.&lt;/p&gt;

&lt;h2&gt;
  
  
  02. Discovering ECSoC’26: Taking the First Step
&lt;/h2&gt;

&lt;p&gt;My introduction to ECSoC’26 came through a friend who suggested that I register for &lt;strong&gt;Elite Coder Summer of Code 2026&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Initially, I was uncertain about participating.&lt;/p&gt;

&lt;p&gt;Although I had some development experience, I lacked a clear understanding of how open-source programs operated in practice. I was unfamiliar with repository selection, issue assignment, maintainer communication, contribution guidelines, and the pull request review process.&lt;/p&gt;

&lt;p&gt;I was interested in participating, but I questioned whether I had sufficient experience.&lt;/p&gt;

&lt;p&gt;A friend's encouragement helped me overcome that hesitation. Instead of waiting until I felt completely prepared, I decided to register and learn through the experience.&lt;/p&gt;

&lt;p&gt;That decision marked the beginning of my ECSoC’26 journey.&lt;/p&gt;

&lt;p&gt;The registration itself was straightforward. Understanding how to make meaningful contributions was the real challenge.&lt;/p&gt;

&lt;p&gt;I needed to learn how to identify suitable projects, understand their technical requirements, navigate unfamiliar codebases, and submit changes that met the expectations of maintainers.&lt;/p&gt;

&lt;h2&gt;
  
  
  03. Building Technical Understanding Through PW IOI
&lt;/h2&gt;

&lt;p&gt;An important part of my preparation came through an initiative introduced by &lt;strong&gt;PW IOI to encourage students to explore open-source development&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Through this initiative, I received guidance from &lt;strong&gt;Abhinav Awasthi Sir and Akash Meruva Sir&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Their mentorship helped me understand the practical aspects of contributing to open-source projects, including:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Exploring repositories and understanding their architecture.&lt;/li&gt;
&lt;li&gt;Reading documentation and contribution guidelines.&lt;/li&gt;
&lt;li&gt;Identifying issues suitable for contribution.&lt;/li&gt;
&lt;li&gt;Understanding GitHub workflows and pull request procedures.&lt;/li&gt;
&lt;li&gt;Communicating effectively with project maintainers.&lt;/li&gt;
&lt;li&gt;Incorporating review feedback and improving implementations.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This guidance helped me connect my existing development knowledge with the actual practices followed by open-source communities.&lt;/p&gt;

&lt;p&gt;I began approaching repositories more systematically, studying their structure, understanding the technologies they used, and identifying issues where I could make meaningful contributions.&lt;/p&gt;

&lt;p&gt;I am sincerely grateful to both mentors for their guidance and for helping me develop the confidence to begin contributing.&lt;/p&gt;

&lt;h2&gt;
  
  
  04. The First Merged Pull Request
&lt;/h2&gt;

&lt;p&gt;The transition from learning about open source to making an actual contribution was an important milestone.&lt;/p&gt;

&lt;p&gt;After exploring several repositories, I identified an issue that aligned with my technical understanding and expressed my interest in working on it.&lt;/p&gt;

&lt;p&gt;Once the issue was assigned, I began examining the relevant code, understanding the existing implementation, and identifying the changes required to address the problem.&lt;/p&gt;

&lt;p&gt;Like most first-time contributors, I had several concerns.&lt;/p&gt;

&lt;p&gt;Would my implementation satisfy the acceptance criteria? Had I understood the issue correctly? Would the maintainer approve the changes?&lt;/p&gt;

&lt;p&gt;Nevertheless, I completed the implementation and submitted my first pull request.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The pull request was merged the following day.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That first successful merge was a defining moment for me.&lt;/p&gt;

&lt;p&gt;It provided practical validation that I could contribute to an existing project, understand its requirements, and deliver changes that met the maintainer's expectations.&lt;/p&gt;

&lt;p&gt;More importantly, it changed how I viewed open-source development.&lt;/p&gt;

&lt;p&gt;I realised that contributing to an established project requires much more than writing code. It involves understanding context, respecting existing architecture, following development standards, communicating clearly, and responding constructively to feedback.&lt;/p&gt;

&lt;p&gt;My first merged pull request gave me the confidence to explore more repositories and take on increasingly challenging contributions.&lt;/p&gt;

&lt;h2&gt;
  
  
  05. Expanding My Contributions Across Projects
&lt;/h2&gt;

&lt;p&gt;Following my first successful contribution, I decided to remain actively involved throughout ECSoC’26.&lt;/p&gt;

&lt;p&gt;During July and August, I consistently explored new repositories, analysed open issues, worked on implementations, and submitted pull requests.&lt;/p&gt;

&lt;p&gt;Contributing across multiple projects exposed me to different codebases, development practices, technologies, and engineering approaches.&lt;/p&gt;

&lt;p&gt;Each repository presented a different learning opportunity.&lt;/p&gt;

&lt;p&gt;Some contributions required understanding unfamiliar project structures. Others involved debugging existing implementations, analysing requirements, or modifying code while maintaining compatibility with established functionality.&lt;/p&gt;

&lt;p&gt;The review process also became an important part of my learning.&lt;/p&gt;

&lt;p&gt;Maintainers frequently provided suggestions, requested refinements, or highlighted areas where implementations could be improved. Incorporating this feedback helped me develop a stronger understanding of code quality, maintainability, and collaborative engineering.&lt;/p&gt;

&lt;p&gt;Balancing contributions with academic responsibilities was another significant challenge.&lt;/p&gt;

&lt;p&gt;There were periods when managing college assignments and development work simultaneously required careful planning and discipline.&lt;/p&gt;

&lt;p&gt;Rather than focusing only on the number of contributions, I gradually developed a more consistent approach to learning and problem-solving.&lt;/p&gt;

&lt;p&gt;During this period, I also maintained a &lt;strong&gt;35-day GitHub contribution streak&lt;/strong&gt;, reflecting my commitment to making continuous progress.&lt;/p&gt;

&lt;h2&gt;
  
  
  06. ECSoC’26: Achievements and Milestones
&lt;/h2&gt;

&lt;p&gt;By August 31, 2026, my participation in ECSoC’26 had resulted in several milestones that I am proud to share.&lt;/p&gt;

&lt;h3&gt;
  
  
  Key achievements
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Achievement&lt;/th&gt;
&lt;th&gt;Result&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;ECSoC’26 Global Rank&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;48&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Merged Pull Requests&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;117&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Open-Source Projects&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;16&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GitHub Contribution Streak&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;35 days&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Total Program Participants&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Approximately 13,000&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Active Contributors&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;822&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Securing 48th rank was a significant achievement, but the numbers alone do not capture the complete experience.&lt;/p&gt;

&lt;p&gt;Each merged pull request represented an opportunity to understand a problem, analyse an existing implementation, develop a solution, and collaborate with maintainers.&lt;/p&gt;

&lt;p&gt;Contributing to 16 different projects strengthened my ability to adapt to unfamiliar codebases and work across different development environments.&lt;/p&gt;

&lt;p&gt;The experience also helped me become more independent in identifying problems, researching solutions, and implementing changes.&lt;/p&gt;

&lt;p&gt;Most importantly, it reinforced my understanding that technical growth comes through consistent practical engagement.&lt;/p&gt;

&lt;h2&gt;
  
  
  07. Recognition by PW IOI
&lt;/h2&gt;

&lt;p&gt;One of the most memorable highlights of this journey was having our ECSoC’26 achievement featured on the &lt;strong&gt;official PW IOI Instagram platform&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Being recognised by the institution's official platform was a meaningful moment, particularly because PW IOI had also played an important role in providing the learning environment and guidance that helped me begin my open-source journey.&lt;/p&gt;

&lt;p&gt;The recognition made the achievement even more special and highlighted the importance of encouraging students to participate in practical learning opportunities beyond the classroom.&lt;/p&gt;

&lt;p&gt;I am grateful to PW IOI for supporting initiatives that expose students to real-world development practices, technical communities, and opportunities for professional growth.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Official recognition:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.instagram.com/p/DfE_2I4k9qN/?img_index=1" rel="noopener noreferrer"&gt;View the ECSoC’26 Feature on PW IOI's Official Instagram&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.pwioi.com/" rel="noopener noreferrer"&gt;Visit the Official PW IOI Website&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  08. Technical and Professional Learnings
&lt;/h2&gt;

&lt;p&gt;Beyond the final ranking and contribution statistics, ECSoC’26 helped me develop several skills that will remain valuable throughout my software engineering journey.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Working with existing codebases&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I developed greater confidence in navigating unfamiliar repositories, understanding existing architecture, identifying dependencies, and making changes within established project structures.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Version control and collaborative workflows&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Regular contributions strengthened my understanding of Git, GitHub, branches, commits, pull requests, and collaborative development practices.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Code quality and maintainability&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Working with maintainers and responding to reviews helped me understand the importance of writing clean, readable, maintainable code that follows project conventions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Technical problem-solving&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Different issues required different approaches to debugging, research, implementation, and testing. This improved my ability to approach unfamiliar technical problems systematically.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Communication and collaboration&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Interacting with maintainers helped me understand how to communicate technical decisions, clarify requirements, discuss implementation approaches, and respond professionally to feedback.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Discipline and time management&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Maintaining regular contributions alongside academic responsibilities strengthened my ability to manage time and work consistently toward long-term goals.&lt;/p&gt;

&lt;p&gt;These experiences have helped me develop a more practical understanding of software engineering and collaborative development.&lt;/p&gt;

&lt;h2&gt;
  
  
  09. Advice for Students Beginning Their Open-Source Journey
&lt;/h2&gt;

&lt;p&gt;For students who are interested in open source but are unsure about where to begin, my biggest recommendation is to start with what you already know and build from there.&lt;/p&gt;

&lt;p&gt;You do not need to master every technology or understand every aspect of software engineering before making your first contribution.&lt;/p&gt;

&lt;p&gt;Start by becoming comfortable with Git and GitHub. Explore repositories that interest you, read their documentation, understand their contribution guidelines, and identify issues that match your current skill level.&lt;/p&gt;

&lt;p&gt;Do not hesitate to ask maintainers for clarification when necessary.&lt;/p&gt;

&lt;p&gt;Your first contribution may require several attempts. Your pull request might receive review comments, and your implementation may need modifications before it is accepted.&lt;/p&gt;

&lt;p&gt;These are normal parts of collaborative software development.&lt;/p&gt;

&lt;p&gt;Instead of viewing feedback as rejection, treat it as an opportunity to improve your technical understanding.&lt;/p&gt;

&lt;p&gt;Most importantly, focus on learning rather than comparing your progress with someone else's achievements.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You do not have to be an expert to contribute to open source. You have to be willing to learn, collaborate, and improve with every contribution.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  10. Acknowledgements
&lt;/h2&gt;

&lt;p&gt;This journey has been shaped by the support, encouragement, and guidance of several individuals and communities.&lt;/p&gt;

&lt;p&gt;I would like to express my sincere gratitude to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;My friend&lt;/strong&gt;, whose encouragement motivated me to register for ECSoC’26 when I was initially hesitant.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PW LeapX&lt;/strong&gt;, for providing my first internship experience and introducing me to collaborative software development.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PW IOI&lt;/strong&gt;, for creating valuable learning opportunities and encouraging students to participate in open-source initiatives.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Abhinav Awasthi Sir and Akash Meruva Sir&lt;/strong&gt;, for their mentorship, guidance, and support in helping me understand the open-source contribution process.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open-source maintainers and developer communities&lt;/strong&gt;, for reviewing my contributions, sharing constructive feedback, and providing an environment for continuous learning.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I am thankful to everyone who contributed to this experience and helped make it a memorable milestone in my journey.&lt;/p&gt;

&lt;h2&gt;
  
  
  Looking Forward
&lt;/h2&gt;

&lt;p&gt;ECSoC’26 has been an important milestone in my development journey, but I consider it a foundation for what comes next.&lt;/p&gt;

&lt;p&gt;The experience has strengthened my interest in open-source software development and encouraged me to continue contributing to meaningful projects, exploring new technologies, and collaborating with developers across different communities.&lt;/p&gt;

&lt;p&gt;From being uncertain about my first contribution to achieving 48th rank, this journey has reinforced an important lesson: progress begins when we are willing to step beyond our comfort zone and learn through experience.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;117 merged pull requests. 16 open-source projects. A 35-day contribution streak. One transformative learning experience.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;These milestones represent not only what I accomplished during ECSoC’26, but also the skills, confidence, and perspective I gained along the way.&lt;/p&gt;

&lt;p&gt;I look forward to building on this experience, taking on new challenges, and contributing to the open-source ecosystem in the future.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The journey continues.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Connect With Me
&lt;/h2&gt;

&lt;p&gt;I welcome opportunities to connect with developers, open-source contributors, technology enthusiasts, and communities working on meaningful projects.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/shahkhushi0307" rel="noopener noreferrer"&gt;github.com/shahkhushi0307&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;LinkedIn:&lt;/strong&gt; &lt;a href="https://www.linkedin.com/in/khushi-shah-31257b381/" rel="noopener noreferrer"&gt;Khushi Shah&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instagram:&lt;/strong&gt; &lt;a href="https://www.instagram.com/_khushishah_03/" rel="noopener noreferrer"&gt;@_khushishah_03&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  ECSoC’26 Achievement Resources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ecsoc-beta.vercel.app/profile/contributor/shahkhushi0307" rel="noopener noreferrer"&gt;ECSoC’26 Contributor Profile&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ecsoc-beta.vercel.app/leaderboard" rel="noopener noreferrer"&gt;ECSoC’26 Official Leaderboard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/drive/folders/1Npv1_jiCZpw2syRPEl-I4fBS-SANy_ta?usp=drive_link" rel="noopener noreferrer"&gt;Certificates and Supporting Documents&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.instagram.com/p/DfE_2I4k9qN/?img_index=1" rel="noopener noreferrer"&gt;PW IOI Official Instagram Feature&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>opensource</category>
      <category>github</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
