For whoever runs a hands-on workshop at a developer event
Lab ReadyForty laptops open at once. What breaks first?
Describe the session, the room, the helpers, what the exercise needs and what the venue said about the network. Free in your browser: how many seats you can really run - the lowest of the room, the helpers and the kit - whether your helpers can actually debug, the prerequisites split into knowledge, machine and accounts, what to do about the network, and an agenda that leaves time for setup. A run writes the delivery sheet, or the pre-flight note for participants.
1 The session and its room free
2 The session, as it will run free
What the page flags
Capacity - three ceilings, the lowest binds
Who unsticks a stuck participant
The prerequisite sheet
The agenda against the booked length
Hands-on, coverage, prerequisites, network
3 Delivery sheet or pre-flight note metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Hands-on and capacity
Coverage
Prerequisites
Network
Agenda
Materials
Triggers for next edition
Checks
Record
Caveats
The page's check of this reply
4 Saved workshops
How it works
First decide whether hands go on keyboards at all - only for what reading cannot teach. Then size help from people who can debug the material: the Carpentries convention is one helper per 8-10 learners on top of two instructors, and logistics volunteers do not count. Capacity is three ceilings on one number - the room, the helpers' reach and whatever is genuinely limited (boards, logins, licence seats) - and the lowest one binds.
Prerequisites come in three kinds, and accounts are the one everyone forgets until minute zero. A venue's "the WiFi is fine" is not an answer: get bandwidth, device count and blocked protocols in writing, and if anyone installs during the session, assume nothing. Open with at least 20 minutes of machine checks, give every exercise a checkpoint, and publish how long the material stays up.