Darasa Hub - Learning Lions
Dira Portal Safety and Welfare ICT Support
SCS3.5

Apps Script

Level 2 · BootCampSCS3 WorkspaceTaught week 5 Thursday after lunch

Submit Your Work

What You Turn In

  1. Photo of your spec with the trainer's initials
    1. One page: the owner's problem, the pattern, the trigger, what it reads, writes and never touches, two tests worked by hand, the edge case; initialled and dated before your first prompt
  2. Your script and its history (repo link)
    1. The draft committed exactly as the tool gave it, then your one-line hand patch committed on its own; 'AI-assisted, directed by <handle>' in the first comment
  3. Your reading log, test log, nine breaks and receipt log (repo link) fill in on the hub
    1. Every line in your own words; two tests and the edge case passing, expected beside actual; each break answered with a line number or a patch; your prompt word for word
  4. The editor copy and the tested copy — stay in the evidence folder
    1. Your script copied from the editor and the copy sheet as .xlsx in ~/scs/evidence/scs3.5; never in the repo
  5. Screenshot of the output tab and the signed Definition of Done fill in on the hub
    1. Nine lines with evidence, signed by the coach after you defended any line live
  6. The owner's how-to-run card (client folder)
    1. In the owner's language: what it does, how it runs, what to do if it stops, who to call
  7. check-scs3.5 receipt and your method note
    1. Every automatic item PASS or explained to a coach; six lines, the sixth a real doubt

Stuck, or want to check your thinking? Paste this card into your own AI and ask it to question you, not answer for you.

How

  1. Asha, by the week 6 Saturday update.
Done when
  1. Spec, initialled before any prompt: One page: owner's problem, pattern, trigger, reads, writes, never touches, two hand-worked tests, the edge case; trainer's initial dated no later than the first prompt on the receipt log
  2. The script .gs with its history: Draft committed exactly as it came, then at least one one-line hand patch committed on its own; labelled 'AI-assisted, directed by <handle>'; same as the editor's copy
  3. Reading log, test log, breaks, receipt log: Every code line on the reading log in plain words; two tests and the edge case passing with expected beside actual; nine breaks each with a line number or a patch; the prompt word for word with the initial's date
  4. Editor copy + tested copy .xlsx: Script copied from the editor; the copy sheet named as a copy with the real rows cleared; the client's real sheet untouched
  5. Output-tab screenshot + signed Definition of Done: Nine lines with evidence, signed by the coach after the live defence: any line, no notes, tests re-run on the copy
  6. Owner's how-to-run card: In the owner's language: what it does, how to run it or when it runs, what to do if it stops, who to call; could be followed without a call
  7. check-scs3.5 receipt + method note: Fourteen automatic items PASS or each NOT YET explained to the coach; six lines, the sixth a real doubt and how to find out

Counts toward: the SCS3.5 badge, 1 to 3 stars · the client folder · attendance for the Taught and SGL blocks · LP (Lion Points) for accepted badge work.

Fill in the worksheet Submit work for SCS3.5