How software works team session

Before the session

Read Days 31, 35 and 38 (about five minutes each), or Module 4 on the cheat sheet.

The 30 minutes

1. 0–5 minOpen

   Quick round: name one error message that stopped you this month.

2. 5–15 minDiscuss three days
   • Day 31: The restaurant model.In the tools we're building, what sits in the dining room that belongs in the kitchen?
   • Day 35: Settings outside the code.Where do our keys and passwords live today, and who could see them?
   • Day 38: Errors are clues, not failures.When something breaks, where do we look first, and what do we hand the agent?
3. 15–25 minExercise: Map one tool

   Pick one tool the team is building. Draw it as the restaurant: what users see, what runs on the server, where the data is kept and where each secret lives. Circle anything in the wrong place.

4. 25–30 minAction for the week

   Each person checks one project for keys or passwords in the code, moves them to a .env file, and confirms .env is in .gitignore.

   Agree the team rule: “Code is shared. Secrets are not.”