Working in a team: standups, Git and code review
How developers work together without breaking each other’s work.
The daily standup
A short daily meeting, often 10 minutes, standing up so nobody makes speeches. Each person answers three things: what I did yesterday, what I will do today, and what is blocking me. Our daily work report is the written form of the same habit.
Write today’s daily work report →
Git workflow in a team
- Never work directly on main. Create a branch per task: feature/cart-page.
- Commit small, with clear messages: "Fix total when cart is empty".
- Open a pull request (PR) with what changed and how to test it.
- A teammate reviews; you fix the comments; then it is merged.
Code review manners
| When you review | When you are reviewed |
|---|---|
| Comment on the code, not the person | Do not take comments personally |
Explain why: "This breaks if the list is empty" | Ask if a comment is unclear |
| Say what is good too | Reply to every comment: fixed, or why not |
| Approve when it is good enough, not perfect | Thank the reviewer |
The 30-minute rule
Stuck? Try alone for 30 minutes: read the error, search, test a small idea. Still stuck? Ask, and say what you tried. Asking after 3 days of silence is the most expensive mistake a junior makes.
🎭 What would you do?
You have been stuck on a bug for most of the day. The deadline is tomorrow.