Objective

After the Onboarding steps, engineers jump into our Github works with less guidance, it could take them days to weeks to get familiar with our codebase, tech stacks, and development rules. Without a training program they could get lost, struggling or the worst, give up and leave. To boost this process and shorten the learning period, this program tries to collect existing documents and develop new ones that can help our new joiners to smooth the learning process, bring engineers up to speed quickly, improve the volunteering experience and engineering productivity.

Program Lead / Coordinators

Ideally, we'll need at least one program lead/Coordinator for each team to track status for Mob programming and Resources, their responsibility includes:

tracking resources status, figuring out what's the missing resource now in the team
coordinate with content producer to upload new resources and share with team members
schedule Mob programming meetings, remind meeting attendees about meeting objectives
Record Mob programming meetings, upload and share with team members

Mob programming (Experiment)

Mob programming (Weekly) for engineers get together to fix and learn from each other

Every engineer can join, video will be recorded and shared within Slack channel (e.g. #engineering-mob-programming)
At the beginning of the meeting, let engineers know this is to be recorded and shared, encourage verbal explanations
Engineers choose one feature to fix / implement on the day, topics should vary to cover more topics from week to week
- topics candidates: UI modification, Authentication, API issue, Code Review, DB Model, Android, IOS, Web3, ...
After posting on the Slack channel, people can comment in the thread for better solution, suggestions, etc.
Senior Engineers can review and make notes or comments on what can be improved

Mob Programming

Resources

Keep tracking our resources below, write documents, produce videos, expose these resource to engineers in different teams as references

( For new created content, will need Senior Engineers' review before publish )

<aside> 💡 Note: Contents below tend to be changed. Leaders from the different teams have the best knowledge of what should be included (please add items you believe is necessary).

</aside>