Qobelarin turns technical learning into a working rehearsal: read the scene, isolate the fault, make the fix, and explain the choice in the room.
Choose an act to see the practical tension it introduces. Each is a different way of staying useful when the code is not cooperating.
Start with the actual behaviour: inputs, outputs, timing, environment and the people who need to understand the next move. We practise turning scattered observations into a shared, testable scene.
PRE-SHOW / READY YOUR DESKThis is not a spectator course. The useful preparation is modest: set up a place to run experiments, a way to record what changed, and enough attention to say what you saw.
No specific operating system or editor is required for the workshop language. Technical setup details are confirmed in the course brief.
evidence is part of the deliverable.INTERACTION NOTE: each cue opens its backstage note without leaving the scene.
These tracks are ways to revisit the same useful habits at different levels of complexity. Scroll the rail horizontally when the stage is narrow.
Map the running parts and make a shared sketch of what is supposed to happen.
Use small experiments to narrow an uncertain claim instead of widening the problem.
Give your investigation a structure another person can inspect and build upon.
Revisit the condition, confirm the new behavior, and decide what belongs in the record.
The tools are familiar. The point is to use them deliberately: as instruments for seeing, checking, and communicating rather than decorations for a technical performance.
| Instrument | Use in rehearsal | Bring / access |
|---|---|---|
| Browser devtools | Inspect the runtime scene | Local browser |
| Text editor | Make a precise, reversible change | Your preference |
| Notes file | Keep evidence and next cues visible | Any plain text tool |
| Repository copy | Try changes without improvising on production | Course brief |
Before changing a line, we practise asking what the code expects, what it changes, and which parts of the system can notice. The annotations are prompts—not a substitute for looking at the whole scene.
Bring a scene to readWhen a change is shown, the room is invited to ask: what was observed, what assumption was tested, what changed, and what would make the conclusion stronger? The goal is a more inspectable decision, not a louder opinion.
Read workshop questionsA review at Qobelarin is a written and demonstrated account of a piece of work. It values the clarity of the investigation and the condition of the hand-off; it does not pretend to be a universal score of talent.
What was expected, what was observed, and where did the discrepancy appear?
Which checks were run and what did each one make more or less likely?
What changed, why was it limited that way, and how was it checked afterward?
What remains uncertain, deferred, or worth testing in a later rehearsal?
The short answers are deliberately not slogans. A workshop is easier to choose when its limits and habits are described plainly.
Tell us what you want to rehearse, what kind of technical scene you are working with, and whether you need a course brief. This browser-only form will confirm your note on this device.