Session 1: Baseline Measurement Handout

This is what we work through together in the session. Follow along in your own clone. We run npm run ci on OrbitTasks live and read the results together. Record what we find in your logbook as we go.

---

Part 1: Timings (numbers)

We run npm run ci from the repo root together. The wrapper script writes a log to baseline.log. We read the per-stage durations off the log live, stage by stage:

#	Stage	Command
1	install	npm install
2	lint	npm run lint
3	typecheck	npm run typecheck
4	test:api	npm run test --workspace=apps/api
5	test:web	npm run test --workspace=apps/web
6	build:api	npm run build --workspace=apps/api
7	build:web	npm run build --workspace=apps/web
8	deploy (simulated)	bash scripts/deploy.sh

Record each stage's duration and pass/fail outcome, plus the total wall-clock time, in your logbook as we go.

Note: a FAIL in a test stage (test:api or test:web) is expected. The suite has flaky tests that fail ~50% of runs. We record it as data and move on.

---

Part 2: Annotated workflow

Below is the canonical flow. As we go, we annotate each stage with how long it took and one observation in plain words. We do this together on screen; you record yours in your logbook.

   ┌──────────────┐     ┌──────────────┐     ┌──────────────┐
   │   install    │ ──▶ │     lint     │ ──▶ │     test     │
   └──────────────┘     └──────────────┘     └──────────────┘

   ┌──────────────┐     ┌──────────────┐
   │    build     │ ──▶ │    deploy    │
   └──────────────┘     └──────────────┘

---

Part 3: Observations (qualitative)

As the pipeline runs, we talk through these together. First instinct is fine. Capture your answers in your logbook:

• Which stage felt the slowest?
• Did any test fail? If yes, which one and what was the error?
• If we run the test suite a second time, do the same things pass / fail?
• Anything that confused you, surprised you, or seemed redundant?

---

Part 4: A gut-feel guess

Before we move on, we each write down a gut answer to:

"If I could fix exactly one thing about this pipeline to make it faster, I would fix..."

Record it in your logbook. No wrong answers. We'll see how the gut compares to the data in Session 2.

---

Keep your logbook

Everything above lives in your logbook. This is continuity, not an assignment: we reuse your Workshop 1 baseline numbers in Workshop 6, and everything in Workshop 8. If we couldn't get a clean run today, that's fine, we fill in the gaps together next session.