Become An Open Source Master [Part 20] - Share What You Learn

Share what you learn as you go on your open-source journey. We can add comments to the code, write wiki pages or articles, or even file issues in the codebase to better understand. When we're ready to start contributing, we should pick a task, dive into the code, and start experimenting with it by adding print statements or breakpoints. This will help us get familiar with the code and the build process so that we can be more effective when making meaningful contributions.

Video reference: [10 Things I Learned from the jQuery Source](https://www.youtube.com/watch?v=i_qE1iAmjFg)

[How to learn a new codebase fast](https://www.jointaro.com/lesson/DX27hiXPJ4G7Czk2mwLL/how-to-learn-a-new-codebase-fast/).

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 19] - What Opinions Do The Authors Have?

Be aware of the human element in open-source projects. We should understand and follow the project's coding style, including linting and formatting preferences. If the project lacks a style guide or linting rules, we can offer to help create them, but we should always do so with the approval of the original maintainers.

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 18] - What Are The Most Important Modules?

We need to identify the important modules in an open source project. We should understand the configuration items, hot functions, and utility classes. Additionally, we should figure out how the data flows through the project, including its structure, storage, and APIs.

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 17] - How Is The Project Laid Out?

We need to understand the layout and structure of your target open-source project. We should identify the important modules and configuration items, and understand how the data flows through the project. We can also look for the entry points to the code base, such as the top-level file with all the exports or the command line interface.

- [Vue.js on GitHub](https://github.com/vuejs)

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 16] - Understand The Basics

We need to learn the codebase of a new open source project to contribute effectively. It's important to understand the bigger picture instead of focusing on every single line of code. Some questions worth asking when approaching a new codebase are: what is the purpose of the code, what are the opinions of the developers, and how is the code structured?

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 15] - Find The Project Community

It's important to understand the bigger picture instead of focusing on every single line of code. Some questions worth asking when approaching a new codebase are: 

- what is the purpose of the code
- what are the opinions of the developers
- how is the code structured?

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 14] - ReactJS Open Source Repo Case Study

We can make a huge difference to an open source project by spreading the good news about it. Sharing our experiences and knowledge about the project can help it gain more interest and adoption. Even seemingly small actions, like writing a blog post or giving a presentation, can have a significant impact on the project's success.

React project stars: <https://star-history.com/#facebook/react&Date>

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 13] - Dipping Your Toes Into A Project

We can contribute to open source projects in many ways, even without writing code. We can triage issues, work on documentation, improve the website design, or provide translations. We can also become an advocate for the project by promoting it on social media, writing articles, or creating training courses. By contributing to the broader ecosystem, we can help the project succeed and build our own reputation in the community.

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 12] - Identify A First Task

We can start contributing to open source projects by looking for existing issues that we can solve. We can use the "help wanted" or "good first issue" tags to find suitable tasks. Contributing to open source projects is a great way to get involved in the community and make the project better. Check out TinyBase as an example: <https://github.com/tinyplex/tinybase/issues>

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 11] - Go With The Flow

We can contribute to open source projects by either creating something new or picking up existing work. It's important to communicate with the community owner or maintainer and earn their trust. We can do this by opening discussions, being open to feedback, and starting with small, well-defined tasks.

Example strong pull request (PR) from TinyBase: <https://github.com/tinyplex/tinybase/issues/130>

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 10] - How To Evaluate A Project’s Health

We can evaluate potential open-source projects by examining their issues and community interactions:

- **Analyze the Issues tab**: Look for a healthy ratio of solved to open issues, evidence of tagging and triage, and positive community engagement. Check for responsiveness to older issues.
- **Observe conversations around issues and pull requests:** Get a sense of the community's dynamics, code quality standards, and how welcoming they are to new contributors.
- **Check the Discussions tab (if available):** See how the community debates future changes and get a feel for the project's overall vibe.
- **Utilize the Insights tab:** Look at statistics like open and closed pull requests, active issues, and contributors to gauge the project's activity level.

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 9] - Solve A Need

When choosing an open-source project to contribute to, we should:

- **Focus on solving a need:** Choose a project that you'll benefit from and have a passion for working on.
- **Assess the project's health:** Look for signs of active maintenance, such as merged pull requests and recent activity.
- **Seek insights from others:** Talk to people who have worked on the project to get their perspectives on the community and development process.

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 8] - Find Companies Active In Open Source

The video discusses where to find open source projects to contribute to.

- The GitHub Octaverse Report and websites like <https://gitstar-ranking.com/> provide lists and rankings of companies and projects active in open source.
- Many large tech companies, like Microsoft and Google, have active open source ecosystems.
- The GitHub trending pages can help you discover new and interesting projects that are gaining popularity.
- Don't limit yourself to one type of project or technology; contributing to a variety of projects will broaden your skills and experience.

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 7] - Improve Something You Use

The video advises that we should start by finding a project that we're passionate about, rather than aiming for the biggest or most well-known ones.

- **Choose projects that you already use or are familiar with**, as this gives you a head start in understanding the project's goals and potential areas for improvement.
- **The dependency graph on GitHub can help you identify potential projects** by showing the dependencies of projects you're already working on.
- **Consider contributing to smaller or medium-sized projects by companies**, as these can offer valuable learning experiences and opportunities to build relationships with professional developers.
- **Contributing to open source can lead to career opportunities**, as demonstrated by the example of Sophie Alpert and her work on the React project.

Article shown by Sophie Alpert: [Using React to speed up the Khan Academy question editor](https://sophiebits.com/2013/06/09/using-react-to-speed-up-khan-academy)

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 6] - The Right Reason To Do Open Source

The video emphasizes that we should approach open source with the right motivations, focusing on the long-term benefits rather than seeking quick career gains.

- **It's not a shortcut to a job:** Open source requires dedication and time; it's not a quick fix for career advancement.
- **Authentic contributions matter:** Open source work is transparent, showcasing your genuine skills and passion to potential employers.
- **Patience is key:** It takes time to learn, contribute meaningfully, and build relationships in the open source community.
- **Focus on the right reasons:** The primary benefits include making an impact, learning and growing, joining a community, and demonstrating your passion for building.
- **Embrace the challenge:** Navigating large, complex projects and overcoming obstacles in open source can develop valuable professional skills applicable to any work environment.

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 5] - The Benefits Of Open Source

We'll discuss the reasons why you should get involved in open source and the benefits it can bring, both professionally and personally.

- **Work on code that matters:** Contribute to projects used by others, gaining a sense of achievement and pride.
- **Improve your coding skills:** Receive feedback and learn from experienced developers, improving your coding abilities and knowledge.
- **Build relationships:** Connect with maintainers, contributors, and users, expanding your network and learning opportunities.
- **Enhance your professional portfolio:** Showcase your skills and experience to potential employers through your open source contributions.
- **Grow your personal reputation:** Gain recognition and build valuable connections within the open source community.

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 4] - Open Source Terminology: Projects, Repos, Issues, PRs

We'll focus on GitHub, a popular platform for open-source software, to understand key terms and concepts.

- Projects and repositories (repos) are the core units of open-source projects on GitHub.
- You can view source code, metadata, and community activity within a repository.
- Issues are used to report bugs or request features, while pull requests propose code contributions.
- Pull requests are reviewed and discussed by the community before being accepted into the project.

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 3] - What Is Open Source?

We'll start with an introduction to open source, which encompasses not just software but also data, education, standards, hardware, and access.

- Open-source software is released under a license that allows users to use, study, change, and distribute it for any purpose.
- There are various open source licenses with different levels of permissiveness, but for this course, we'll focus on projects under the MIT license.
- Open-source code empowers users to study and adapt software to their needs, similar to how user scripts or custom style sheets modify websites.
- You can learn from open-source projects like React to understand how companies build complex systems.
- If you make changes, you can fork the project or submit your changes back to the original project through a pull request.

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 2] - How This Course Works

We'll explore the benefits of open source and how to contribute to existing projects in this course.

- Understand the benefits of open source and the mindset needed to work effectively in the open source ecosystem
- Learn how to get involved in someone else's project, understand their codebase, and make meaningful contributions
- Explore how contributing to open source can benefit your career by showcasing your skills and building your professional profile.
- This course won't cover how to create your own open source project or what it's like to work on one from within a company.

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

How Managers Hire Great Engineers [Part 25] - Conclusion

Congratulations on making it to the end of the course! Please go and hire awesome people now :) 

Connect with John Egan on LinkedIn: <https://www.linkedin.com/in/jwegan/>

Tech Career Growth Videos

Our instructional videos provide software engineers with insights needed for career growth. Masterclasses go incredibly in-depth on a specific tech topic while case studies are real examples from established engineering leaders.