## Chapter 28 — Field practice ### Lesson map Lesson 28 published. Map, example, EX082. ```mermaid flowchart TD N0["Learning outcomes"] N1["28.1 Working in the field"] N2["28.2 Unexpected tasks"] N3["28.3 Reflecting on practice"] N4["Synthesis"] N0 --> N1 --> N2 --> N3 --> N4 N4 --> EX["Worked example"] EX --> Q["Exercise EX082"] ``` ### Logical drawing ```mermaid flowchart LR N0["Learning outcomes"] N1["28.1 Working in the field"] N2["28.2 Unexpected tasks"] N3["28.3 Reflecting on practice"] N4["Synthesis"] N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX082"] ``` ```text [Learning outcomes] | v [28.1 Working in the field] | v [28.2 Unexpected tasks] | v [28.3 Reflecting on practice] | v [Synthesis] | v [Worked example] --> [Exercise EX082] ``` ### Learning outcomes You will (1) work in a real operational setting; (2) handle routine and unexpected tasks; (3) reflect on professional practice. ### 28.1 Working in the field Lucas spends a term working with the makerspace's volunteers two days a week. He handles routine tasks, such as monthly maintenance and checklist reviews, and helps with member questions about credits. He learns the rhythm of the organisation: busy evenings, quiet mornings and a monthly board meeting where decisions are made. Field practice shows him that technical work happens among people with other priorities. He schedules maintenance in quiet mornings and brings proposals to the board with short written summaries that members can read beforehand. ### 28.2 Unexpected tasks One afternoon a member reports that their phone was stolen and asks whether their credits are safe. Lucas follows the runbook: he helps the member contact staff, who verify their identity in person, and the signers approve moving the member's credits to a new address under the documented process. The old address is noted in monitoring. Another day a node's server loses power; the other two keep the ledger running and Lucas restarts it after power returns. Handling unexpected tasks calmly depends on preparation done long before. ### 28.3 Reflecting on practice Lucas keeps a weekly journal. He notes that his early explanations to members were too technical and that drawings helped. He reflects on an ethical moment: a volunteer asked him to look up another member's booking history out of curiosity, and he declined, explaining that access is for operational need only. Reflection helps him see his own development. Ms Adebayo reads the journal and discusses it with him monthly. She notes that professional judgement grows through practice and honest reflection, not from technical knowledge alone. ### Worked example Lucas helps move a member's credits after a stolen phone using the documented process and declines a curiosity request for booking history. > **Synthetic case.** The placement and events are synthetic. ### Errors and limits Looking up member data out of curiosity breaches the principle of access for need only. ### Exercises - **EX082 — Maintenance timing.** When does Lucas schedule maintenance? *Rubric:* 3 = quiet mornings;; 2 = mornings;; 1 = busy evenings;; 0 = none. - **EX083 — Stolen phone response.** How are a member's credits protected after phone theft? *Rubric:* 3 = verified in person and moved to a new address by signers;; 2 = moved;; 1 = vague;; 0 = none. - **EX084 — Declined request.** What did Lucas decline? *Rubric:* 3 = looking up another member's booking history;; 2 = curiosity lookup;; 1 = a raise;; 0 = none. ### Synthesis Field practice and reflection build the judgement that technical knowledge alone cannot. ### Continue studying — chapter 28 of 30 [← Chapter 27 (draft)](#ch-27) · [Course chapter index](../SUBJECTS.md) · [Chapter 29 (draft) →](#ch-29) ## Worked answers **EX082.** In quiet mornings. **EX083.** After in-person identity checks, signers move the credits to a new address. **EX084.** A volunteer's request to look up another member's booking history.