Compilers & Teamwork
Goal: Hear how Holly Borla grew as a developer and how clear communication helps teams (and beginners) make progress.
Choose one
Please listen to one of the following interviews:
- ATP — “Interview: Holly Borla & Ben Cohen” — Holly talks about working on Swift, learning from others, and how teams decide what to build.
- Swift by Sundell #69 — “Swift Playgrounds” (with Holly Borla & Grace Kendall) — A hopeful discussion about learning with Playgrounds and how helpful error messages can guide you.
Before you listen
- In one sentence, write something you’re curious about (learning from mistakes, reading other people’s code, etc.):
While you listen
- Write 3 short notes you want to remember:
1.
2.
3.
Afterwards
- Reading code first: What’s one benefit of looking at existing code or examples before you start typing?
- Mindset: What attitude did Holly model that you want to emulate? Explain why.
- Teachback: In 3–4 bullets, explain “what a compiler does” using an analogy (kitchen, assembly line, etc.).
Extension
- Make a teamwork checklist for our class. How can someone be a good member of a team?
Curriculum alignment
- A4 — read existing code before changes; use compiler messages to diagnose and validate fixes.
- B2 — communicate clearly in teams (simple summaries, named intentions) to align design decisions.
- B4 — practice status updates and reflective notes that explain the problem, approach, and tests.
- C3 — understand tools: how IDEs, compilers, and interpreters work together to run your code.
- D2/D3 — glimpse compiler work and real developer roles; connect interests to post‑secondary paths.