<?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: Asokumar Dhusanthika</title>
    <description>The latest articles on DEV Community by Asokumar Dhusanthika (@thusanthika2003).</description>
    <link>https://dev.to/thusanthika2003</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%2F4198718%2F33ef77ae-1010-4ed5-be33-42afbd1aa836.png</url>
      <title>DEV Community: Asokumar Dhusanthika</title>
      <link>https://dev.to/thusanthika2003</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/thusanthika2003"/>
    <language>en</language>
    <item>
      <title>How Open Source Turns Learning into Collaboration</title>
      <dc:creator>Asokumar Dhusanthika</dc:creator>
      <pubDate>Tue, 27 Oct 2026 04:41:01 +0000</pubDate>
      <link>https://dev.to/thusanthika2003/how-open-source-turns-learning-into-collaboration-1f3</link>
      <guid>https://dev.to/thusanthika2003/how-open-source-turns-learning-into-collaboration-1f3</guid>
      <description>&lt;p&gt;For many students learning to code, the first real challenge is not writing a program. It is figuring out how to work on a project created by someone else.&lt;/p&gt;

&lt;p&gt;There may be unfamiliar folders, hundreds of files, and instructions that are difficult to understand at first. It can feel intimidating to make a change when other people are watching.&lt;/p&gt;

&lt;p&gt;Hacktoberfest offers a reason to take that first step. The annual event encourages people to explore open source and contribute to projects alongside a wider community of developers.&lt;/p&gt;

&lt;p&gt;What is open source?&lt;/p&gt;

&lt;p&gt;Open-source software is software whose source code is made available for people to inspect, use, modify, and share under the terms of its licence.&lt;/p&gt;

&lt;p&gt;Think of it like a recipe that has been shared with a community. People can study how it was made, suggest improvements, and create their own versions, while following the rules set by the recipe’s creator.&lt;/p&gt;

&lt;p&gt;Software projects work in a similar way. Developers share code, and contributors can help improve it. Linux, Mozilla Firefox, and Visual Studio Code are examples of projects with open-source code.&lt;/p&gt;

&lt;p&gt;But open source is more than access to code. It is also a way for people to solve problems together.&lt;/p&gt;

&lt;p&gt;A place for beginners to learn&lt;/p&gt;

&lt;p&gt;A student who is used to university assignments may be surprised by the structure of an open-source project. The work does not begin with writing code. It begins with reading.&lt;/p&gt;

&lt;p&gt;A contributor might first explore the project’s documentation, understand how to run it, and look at its list of issues. An issue is a task, problem, or suggestion recorded by the community. Some projects label suitable tasks as good first issues to help new contributors find a starting point.&lt;/p&gt;

&lt;p&gt;The first contribution does not have to be a major feature. Correcting an unclear instruction, fixing a broken link, improving an example, or reporting a bug can make a project more useful for everyone.&lt;/p&gt;

&lt;p&gt;Small contributions also help beginners become familiar with the process before attempting larger changes.&lt;/p&gt;

&lt;p&gt;Understanding Git and GitHub&lt;/p&gt;

&lt;p&gt;Two tools often appear in the open-source journey: Git and GitHub.&lt;/p&gt;

&lt;p&gt;Git is a version-control tool. It records changes to files so developers can follow the history of a project and work on changes in an organised way.&lt;/p&gt;

&lt;p&gt;GitHub is a platform where people can host Git repositories and collaborate. A repository contains a project’s files and their version history.&lt;/p&gt;

&lt;p&gt;A common contribution process looks like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Find a project and read its contribution guidelines.&lt;/li&gt;
&lt;li&gt;Choose a task that matches your skills.&lt;/li&gt;
&lt;li&gt;Create a copy of the repository, often called a fork.&lt;/li&gt;
&lt;li&gt;Make your changes in a separate branch.&lt;/li&gt;
&lt;li&gt;Save your work in Git using a commit.&lt;/li&gt;
&lt;li&gt;Submit a pull request to propose your changes to the original project.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The project maintainers can review the pull request, ask questions, suggest changes, or accept the contribution.&lt;/p&gt;

&lt;p&gt;Learning these steps takes practice. A confusing error or a requested correction is not a sign that someone does not belong. It is often part of learning how a project works.&lt;/p&gt;

&lt;p&gt;The human side of open source&lt;/p&gt;

&lt;p&gt;Behind every repository are people: maintainers who care for the project, contributors who suggest improvements, and users who rely on the software.&lt;/p&gt;

&lt;p&gt;That is why communication matters. A clear bug report helps others reproduce a problem. A helpful pull request explains what changed and why. A respectful question can make it easier for someone to offer guidance.&lt;/p&gt;

&lt;p&gt;Review is also an important part of collaboration. When a maintainer suggests a change, they may be helping a contributor understand the project’s standards or pointing out a situation the contributor had not considered.&lt;/p&gt;

&lt;p&gt;For students, these interactions are valuable preparation for group projects and future workplaces, where technical work and communication go hand in hand.&lt;/p&gt;

&lt;p&gt;Beyond October&lt;/p&gt;

&lt;p&gt;Hacktoberfest can be an introduction to open source, but the learning does not have to end when the event does.&lt;/p&gt;

&lt;p&gt;Students can continue exploring projects that match their interests, whether those interests are web development, cloud computing, cybersecurity, design, or documentation. Over time, even small contributions can build confidence and a better understanding of how software is developed.&lt;/p&gt;

&lt;p&gt;The most useful first step is simple: find a project that interests you, read its guidelines, and look for a way to help. Every experienced contributor was once new to the process.&lt;/p&gt;

&lt;p&gt;Open source gives us a chance to learn from others—and, when we are ready, help others learn from us too.&lt;/p&gt;

&lt;h1&gt;
  
  
  Hacktoberfest #OpenSource #Git #GitHub #StudentDevelopers #LearningInPublic
&lt;/h1&gt;

</description>
      <category>productivity</category>
      <category>opensource</category>
      <category>github</category>
      <category>git</category>
    </item>
    <item>
      <title>What Hacktoberfest Taught Me About Git, GitHub, and Open-Source Collaboration</title>
      <dc:creator>Asokumar Dhusanthika</dc:creator>
      <pubDate>Sun, 25 Oct 2026 05:44:05 +0000</pubDate>
      <link>https://dev.to/thusanthika2003/what-hacktoberfest-taught-me-about-git-github-and-open-source-collaboration-1pa2</link>
      <guid>https://dev.to/thusanthika2003/what-hacktoberfest-taught-me-about-git-github-and-open-source-collaboration-1pa2</guid>
      <description>&lt;p&gt;As an ICT student, I spend a lot of time learning programming concepts and working on assignments. But learning how to work with other developers is a different experience. Hacktoberfest encouraged me to explore that side of software development and think more seriously about open source.&lt;/p&gt;

&lt;p&gt;When I first started learning Git and GitHub, there were so many terms to understand: repositories, branches, commits, forks, and pull requests. I could remember the commands, but understanding how they fit together took more time.&lt;/p&gt;

&lt;p&gt;Exploring open-source collaboration helped those concepts make sense.&lt;/p&gt;

&lt;p&gt;Git became more than a list of commands&lt;/p&gt;

&lt;p&gt;One of the biggest lessons for me was understanding why version control matters.&lt;/p&gt;

&lt;p&gt;Git keeps a record of changes, which makes it easier to understand how a project develops. Branches give us space to work on a change, while commits help explain the steps we took.&lt;/p&gt;

&lt;p&gt;I also began to appreciate the value of a clear commit message. Writing “updated files” might feel enough at the moment, but it tells the next person very little. A useful message helps someone understand what changed without having to guess.&lt;/p&gt;

&lt;p&gt;These small habits can make teamwork much easier.&lt;/p&gt;

&lt;p&gt;GitHub is a place for conversations&lt;/p&gt;

&lt;p&gt;I used to think of GitHub mainly as a place to upload code. Now, I see how much discussion happens around that code.&lt;/p&gt;

&lt;p&gt;An issue explains a problem. A pull request introduces a proposed change. A review gives people a chance to ask questions, suggest improvements, and check whether the change fits the project.&lt;/p&gt;

&lt;p&gt;That process taught me that explaining my work matters too. Someone reviewing a contribution needs to understand the problem, the solution, and how the change was checked.&lt;/p&gt;

&lt;p&gt;Good communication makes the code easier to review.&lt;/p&gt;

&lt;p&gt;Small contributions can still be useful&lt;/p&gt;

&lt;p&gt;As a beginner, it is easy to look at an unfamiliar repository and feel that you have nothing valuable to offer.&lt;/p&gt;

&lt;p&gt;But a project needs more than new features. Clear setup instructions, corrected documentation, helpful examples, and well-described bug reports all help people use and maintain it.&lt;/p&gt;

&lt;p&gt;This changed how I think about contributing. A sensible starting point is finding a small problem I understand and working carefully on it.&lt;/p&gt;

&lt;p&gt;The size of a change does not tell the whole story of its usefulness.&lt;/p&gt;

&lt;p&gt;Collaboration requires patience&lt;/p&gt;

&lt;p&gt;Reading someone else’s code takes time. So does understanding contribution guidelines and learning how a project is organised.&lt;/p&gt;

&lt;p&gt;I am learning to slow down, read first, and ask specific questions when I get stuck. I am also learning to see feedback as part of improving the work. A suggested change is an opportunity to understand something I may have missed.&lt;/p&gt;

&lt;p&gt;What I want to carry forward&lt;/p&gt;

&lt;p&gt;My biggest takeaway from Hacktoberfest is that becoming a better developer includes learning how to contribute responsibly.&lt;/p&gt;

&lt;p&gt;I still have more to learn about Git, GitHub, and working with unfamiliar codebases. But I have a clearer place to start: understand the project, choose a manageable task, communicate clearly, and stay open to feedback.&lt;/p&gt;

&lt;p&gt;Those are habits I want to bring into my university group projects and future work.&lt;/p&gt;

&lt;p&gt;For me, Hacktoberfest is a starting point for continuing to learn with other people—and, little by little, becoming someone who can help them too.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>github</category>
      <category>git</category>
    </item>
  </channel>
</rss>
