Practice how engineers build, review, and improve

An open training ground for turning knowledge into projects, pull requests, technical decisions, feedback, and thoughtful iterations.

Meaningful ProjectsOpen SourceCommunity DrivenVisible Growth

Our Approach

Learn by Doing

Move beyond following tutorials by making decisions in a project of your own or contributing to an open project. The goal is to practice, reflect, and build something you can explain.

Collaborative Growth

Use issues, discussions, and pull requests to work with fellow learners and experienced contributors. Feedback is an opportunity to improve the work, not a score.

Visible Growth

Keep a visible record of what you built, why you made each decision, how you responded to review, and what changed through iteration. That work may support a portfolio without pretending to replace professional employment.

Feedback Opportunities

Ask for review on code and design decisions. Feedback and mentoring depend on contributor availability, so the Hub does not promise an immediate or permanent reviewer.

What this training ground can and cannot do: It can help you practice collaboration, review, documentation, iteration, and ownership. It cannot reproduce every customer, business, operational, or production responsibility of a paid engineering role.

Engineering Ways of Working

Practice habits that matter across teams and locations. Broader opportunities may follow, but the immediate work is learning to build responsibly with other people.

Review and Iteration

Request technical feedback through Pull Requests
Discuss code quality, trade-offs, and maintainability
Improve the work through review when reviewers are available
Build confidence by explaining and revising decisions

Industry Practices

Master Git workflows used in professional teams
Learn collaborative development practices
Understand project documentation standards
Practice agile development methodologies

Community Support

Feedback opportunities from experienced contributors
Questions and technical direction through open discussion
Different perspectives on problem-solving approaches
Support that grows as more contributors become reviewers

Context and Trade-offs

Work from problem statements and practical use cases
Practice interpreting and clarifying requirements
Learn to balance technical and business needs
Discuss constraints without claiming a full production environment

How to Join GitHub Projects

1Create GitHub Profile

Create a professional GitHub profile. If you already have one, go to next step.

Add a clear profile picture and bio
Include your learning goals and interests
Pin your best repositories
Enable two-factor authentication for security

Create GitHub Account

2Send GitHub ID via Facebook

Send your GitHub username through TP Coder Facebook page Direct Message.

Example message: “สวัสดีครับพี่ ผมอยากลองทำ Innovation Hub. GitHub ID: [your-github-username]”

Example GitHub ID: marttp (https://github.com/marttp)

Message TP Coder FB

3Wait for Invitation

Wait for the GitHub organization invitation via email. This usually takes 1-2 business days.

Check your email inbox and spam folder
The invitation will come from GitHub notifications
Click “Accept Invitation” in the email
You'll gain access to the TP Coder Innovation Hub organization

4Let's Explore!

Once you're in, pick a project from our list or come up with your own interest!

Browse the Project and Problem list to find interesting challenges
Pick an existing project that matches your skills and interests
Propose your own project idea if you have something in mind
Join discussions and connect with other contributors

View Project List Innovation Hub

Contribution Guidelines

Freestyle Development

You are free to explore, experiment, and propose solutions in your own style. Pull Requests are the main place to show your reasoning, discuss the work, request feedback, and improve through iteration.

Key principle: Build with ownership, explain your decisions, and leave useful context for the next contributor.

PR-Based Communication

Use Pull Requests as the main way to share your work and get feedback

Describe what you built and why in your PR description

Ask questions and request reviews from other contributors

Learn from feedback and iterate on your solutions

Collaboration Spirit

Experiment freely while staying open to evidence and trade-offs

Share your learning journey and help others learn too

Be supportive and encouraging in code reviews

Celebrate progress and learning, not just perfect code

See What Others Have Built

Explore what contributors built, the ideas they chose, and the work they made visible while practicing their skills.

View Project Showcase