A workshop is a product

Placeholder throughout. This post exists so the pipeline has something real to render — front matter, headings, a listing, both kinds of pull quote and a note — and so the house style can be checked against actual prose rather than a specimen line.

The first time I ran a hardware workshop I treated it as a talk with exercises bolted on. Twenty people, eight boards, and a plan that assumed everything would work. It did not, and the failure was not the hardware.

What I had actually built was a product with no error states. Every path through the room that was not the happy one simply had nothing waiting at the end of it.

Every unhappy path had nothing waiting at the end of it.

Budget for the refusals

The interesting work is in what the system says when it says no. A board that will not flash, a bay that will not release, a link that drops in the middle of a run.

// every path out of the room needs an answer
when (unit.state) {
  Docked   -> prompt("the bay is still holding it")
  Offline  -> prompt("no link. check the bench")
  else     -> run(mission)
}

Every one of those is content, and it needs writing before the day rather than improvising at the table.

What someone else said

The quote below is the other kind: a second voice on the page, so it carries clay rather than moss.

Placeholder. A sentence quoted from a source, an attendee, or a review.

Placeholder attribution

A last paragraph, so the post does not end on a component.