Collaboration
Introduzido| English | Significado |
|---|---|
| software/ˈsɒftweə/ | software |
| program/ˈprəʊɡræm/ | programa |
| Collaboration/kəˌlæbəˈreɪʃn/ | Colaboração |
| Pair programming/peə ˈprəʊɡræmɪŋ/ | Programação em par |
| driver/ˈdraɪvə/ | piloto |
| navigator/ˈnævɪɡeɪtə/ | navegante |
| Clear communication/klɪə kəˌmjuːnɪˈkeɪʃn/ | Comunicação clara |
| Respect/rɪˈspekt/ | Respeito |
| Feedback/ˈfiːdbæk/ | Feedback |
| perspectives/pəˈspektɪvz/ | perspectivas |
| documentation/ˌdɒkjuːmənˈteɪʃn/ | documentação |
| version control/ˈvɜːʃn kənˈtrəʊl/ | controle de versão |
Software is a team sport
- Real software 软件 is almost never built alone.
- A large program 程序 — a set of instructions a computer follows — is designed, written, tested, and fixed by a team.
- Collaboration 协作 means people working together toward a shared goal.
- Learning to work well with others is a core CS skill, not a nice extra.
Collaboration in software means:
Dificuldade 1/5 · Moedas 100 + pequeno bônus na primeira conclusão hoje
A team shares ideas and divides the work toward one goal.
Match each pair-programming role to what they do.
Dificuldade 2/5 · Moedas 140 + pequeno bônus na primeira conclusão hoje
The driver writes; the navigator reviews and thinks ahead. They swap often.
Pair programming
- Pair programming 结对编程 is a structured way for two people to share one computer.
- The driver 驾驶员 types the code.
- The navigator 导航员 watches, thinks ahead, and catches mistakes.
- They swap roles often — two minds on one problem catch errors early.

A jigsaw in progress: collaboration and modular design piece the solution together
Strong or weak collaboration?
Good collaboration means clear communication, respect, feedback on the work, and shared tools — not one person doing everything or attacking teammates.
Good feedback comments on the work, not the person.
Dificuldade 1/5 · Moedas 100 + pequeno bônus na primeira conclusão hoje
That keeps feedback useful and respectful.
One clear benefit of a diverse team is:
Dificuldade 1/5 · Moedas 100 + pequeno bônus na primeira conclusão hoje
Different people notice different problems and solutions.
Habits that make teams work
- Clear communication 沟通: say what you mean, listen, and ask when unsure.
- Respect 尊重: take every teammate's ideas seriously, even in disagreement.
- Feedback 反馈: comment on the work, not the person — and treat feedback you receive as help.
- More people means more perspectives 视角, so blind spots get caught.
A ______ control system records every edit and merges everyone's work.
Dificuldade 1/5 · Moedas 100 + pequeno bônus na primeira conclusão hoje
Version control lets a team combine changes without losing any.
Program documentation is useful because it:
Dificuldade 1/5 · Moedas 100 + pequeno bônus na primeira conclusão hoje
Documentation helps a teammate (or future you) understand the code.
Tools and documentation
- Teams share code with a version control 版本控制 system — it records every edit and merges everyone's work without losing any.
- Good documentation 文档 explains what a program does, so a teammate (or future you) understands it without reading every line.
- Together, these let many people build one program without chaos.
Worked example: a pair stuck on a bug
Mei (driver) and Tom (navigator) are building a quiz app. Tom notices the score never goes above 1, but Mei keeps typing new features. What should they do, and how should Tom give feedback?
- Tom should pause the work and describe the problem in terms of the code: "The score resets to 0 inside the loop, so it never gets past 1." That is feedback on the work, not "you made a mistake."
- They test the fix together, then swap roles, so Tom drives the next feature. In the project log they record who contributed what, as AP CSP's Create task asks you to acknowledge collaboration.
In pair programming, what does the navigator do?
Dificuldade 1/5 · Moedas 100 + pequeno bônus na primeira conclusão hoje
The driver types; the navigator reviews and plans.
A team with members of different backgrounds is more likely to anticipate the needs of different users.
Dificuldade 1/5 · Moedas 100 + pequeno bônus na primeira conclusão hoje
Diverse perspectives help catch problems and bias early.
Software is built by teams, so collaboration matters. Pair programming splits the work into a driver (types) and a navigator (reviews), who swap often. Good teams rely on communication, respect, and feedback on the work — plus version control and documentation to combine everyone's contributions.