Hey GitHub Community! 👋

[Long-Nguyen-dev]

Introduce yourself

Hi everyone! I'm Harry, a full-stack developer who enjoys building things, learning new technologies, and exploring open source.

I'm joining the open-source community because I want to learn how real projects are built, maintained, and improved by developers around the world.
I believe contributing to open source is one of the best ways to grow, not just by writing code, but by collaborating, reviewing ideas, and learning from experienced maintainers.

I'm interested in software architecture, AI tools, automation, backend systems, and developer tools.
I'm still learning, but I'm excited to contribute wherever I can, whether it's fixing bugs, improving documentation, testing features, or helping other developers.

Big thanks to all the maintainers who spend their time building and supporting open-source projects.
Looking forward to learning from you, contributing back, and being part of the community!

If there’s anything you’d like to discuss, please leave a comment on my introduction post.
If you need urgent assistance or quick communication, you can reach me via Slack.

Invitation link: longway.dev

See you around! 🚀

Links (optional)

https://join.slack.com/t/longwaydev-workspace/shared_invite/zt-401pvx5v9-8Lo~ihaZAvNoIpE5bzYy2Q

Where are you in your GitHub journey?

Brand new to GitHub

And where are you going next on GitHub?

My dream is to found a global outsourcing company.
Therefore, I am happy to meet excellent developers here and share ideas.

What technical skills or projects are you working on?

I am a full-stack developer with over 7 years of experience in industries related to SaaS, IoT, and Healthcare.

Got a question for us? (optional)

What's the best way to become a contributor that maintainers genuinely enjoy working with?

[JoaoArnaud]

Welcome, Harry!

Your experience with SaaS, IoT, and healthcare sounds valuable, especially for open-source projects involving backend systems, automation, and developer tooling.

Regarding your question, I think maintainers usually enjoy working with contributors who communicate clearly, respect the project’s existing conventions, and make their contributions easy to review.

Some practices that help a lot are:

• Read the contribution guidelines before starting.
• Discuss larger changes in an issue before implementing them.
• Keep pull requests small and focused.
• Explain what changed, why it changed, and how it was tested.
• Avoid unrelated formatting or refactoring in the same PR.
• Respond respectfully to review feedback.
• Be honest when you are unsure about something.
• Help improve documentation and tests, not only source code.
• Avoid pressuring maintainers for an immediate response.

I also think consistency matters more than making one large contribution. A developer who regularly submits clear, well-tested improvements and communicates professionally will gradually build trust with maintainers.

Good luck with your open-source journey and your goal of building a global company!

[Long-Nguyen-dev]

Thanks for the warm welcome!

Those are really solid tips. I especially like your point about consistency; I'd rather make small, useful contributions over time than try to land one huge PR.

I'll definitely keep all of this in mind as I get more involved in open source. Thanks again, and hopefully we'll get a chance to collaborate on a project someday!

[Mr-Nilarnab]

@Long-Nguyen-dev

Welcome to the GitHub Community, Harry!

With your background in SaaS, IoT, and healthcare, you're bringing valuable real-world experience to open source. One thing I'd add to the excellent advice already shared is that maintainers often remember contributors not just for the code they write, but for how they collaborate.

A few habits that go a long way are:

• Start by understanding the project's goals before proposing changes.
• Reproduce and verify bugs before attempting a fix.
• Keep commit history clean and write meaningful commit messages.
• Be open to feedback and willing to iterate—code reviews are part of the learning process.
• When you have time, help answer questions from other contributors. Building a supportive community is just as valuable as writing code.

Also, don't underestimate documentation, accessibility improvements, and test coverage. These contributions are often highly appreciated and can have a lasting impact.

Wishing you the best on your open-source journey and with your goal of building a global outsourcing company. I hope to see your contributions across many projects in the future!

[Long-Nguyen-dev]

Thanks for your thoughtful reply!

I wish you all the best on your open source journey. I hope you find great teammates, build amazing projects, and learn from one another along the way.

I recently started a Slack community for developers who want to collaborate on open source, exchange ideas, and build genuine connections. It's still in its early days, but we're working to grow an active, supportive community where people can communicate in real time and help each other improve.

If that sounds like something you'd enjoy, you're more than welcome to join us!

Slack: https://join.slack.com/t/longwaydev-workspace/shared_invite/zt-401pvx5v9-8Lo~ihaZAvNoIpE5bzYy2Q

[Mr-Nilarnab]

@Long-Nguyen-dev

Thank you for the kind words, Harry—I really appreciate it!

It's great to see initiatives that encourage developers to collaborate and learn from one another. Building a supportive community where people can exchange ideas, review code, and contribute to open source together can make the learning process much more enjoyable.

I wish you and your community continued success. Hopefully it grows into a place where developers of all experience levels can share knowledge, contribute to meaningful projects, and help each other improve.

Looking forward to seeing your future open-source contributions. Best of luck!