Git, GitHub, and collaboration
Opening notes
Welcome the viewer. Explain that this is one lesson in the eight-part Job-Ready Software Engineering series. Set up the outcome before beginning.
Speaker view / 02
Git, GitHub, and collaboration
Git is a communication tool
Make your work easy to review
Speaker notes
Employers look for evidence that you can work safely with other people. Git gives a team a history of decisions; GitHub gives the team a place to discuss and review them.
The smallest useful workflow
- Pull latest changes
- Create a focused branch
- Make one change
- Inspect the diff
- Commit
- Push
Speaker notes
Explain what each step protects us from. Pull before starting. Use a branch so unfinished work does not affect the shared branch. Inspect the diff before committing.
A good commit tells one story
- Focused scope
- Imperative message
- No unrelated formatting
- Easy to review or revert
Speaker notes
Compare “update files” with “Add application status field.” The second message gives a future teammate a useful clue.
Pull requests are evidence
- What changed?
- Why did it change?
- How was it tested?
- What should reviewers inspect?
- What is out of scope?
Speaker notes
The pull request is where you make your reasoning visible. A reviewer should not have to reconstruct the purpose from the diff alone.
Review in the right order
- Behavior
- Risks and edge cases
- Test evidence
- Maintainability
- Style
Speaker notes
Start with whether the change solves the right problem. Style matters, but it comes after correctness and risk.
Demo: make a Launchpad change
Add status to a job application
Speaker notes
Perform the complete workflow slowly: create a branch, make the change, inspect the diff, commit and push, then write the PR description.
Pause: write the review
- One correctness comment
- One test suggestion
- One question for the author
Speaker notes
Pause the video. Do not hunt for grammar mistakes. Look for behavior, missing cases, and evidence.
Your artifact
- Focused pull request
- Clear title and motivation
- Test evidence
- Screenshot or example request
Speaker notes
This PR is a public work sample. Do not include secrets or employer code. Use Launchpad or a project you own.
Make the artifact.
Publish your work, then continue to the next lesson.
Closing notes
Repeat the artifact viewers should create. Invite them to subscribe and join the future live cohort waitlist.