These are the working agreements our class co-created together in our working session. They define how we run our sessions, what the teacher and students each commit to, and how we keep the class clear, supportive, and productive.

How We Run Working Sessions

• Every session has a clear objective and ends with one tangible output on your own screen — hands-on, building together, not just watching demos.
• Morgan and the whole class use Claude to build live, each on our own computers.
• The teacher sets and shares the session schedule and the specific deliverables we'll complete.
• In-week and weekend sessions follow the same structure; the ~3-hour weekend session repeats the week's content so anyone who missed the first can get the same material.
• We pause during sessions to make sure everyone is keeping up, and we take breaks in the 3-hour session.
• The weekend session gives you a choice: code along with the instructor, work in pairs, work on your own, or opt out.
• Every session and lecture is recorded with a transcript.
• We always start with an agenda set ahead and always end on time.

A Shared Baseline for Mixed Levels

• Each session establishes a shared baseline and the essential vocabulary and process first, then separates core tasks from optional advanced work.
• Not everyone will finish at the same level — but everyone should be able to follow the session and reach the core learning outcome.
• This reflects Tech Fleet's inclusive purpose: giving people opportunity regardless of previous qualifications or experience.

Questions & Office Hours

• The room stays open after each lecture for questions.
• Open office hours on Wednesdays; send questions ahead of time if you can't make it.
• Dedicated time to work on our own projects on Saturdays.

Homework & Deliverables