Coding for Non-Coders covers getting started. This covers what comes after: maintenance, tech debt, architecture you can't undo, reviewing code you didn't write.
6 sessions, monthly, 90 minutes, online, capped at 12 people. Same structure every time, so nobody prepares a format.
Bring one thing that is live, or will be during the cohort, that someone other than you depends on. That is the only requirement.
Applicants rank these. The ranking sets the running order.
Ten minutes. It sets the theme order, when we meet, and what it costs. We send the results to everyone who applies.
How long you have been at it, how many people touch the code, what has broken before: your repository already knows. Paste this into Claude Code, Codex, or any coding agent. It asks what you are building and where to look, reads what it can, asks you the rest, and hands back a filled-in link. It cannot submit for you, and it works whether your product is one repo, several, or not code at all.
Read https://www.envisioning.com/advanced-mode/schema.json and follow its howToUse. Ask me first which product this is about and where to look. Don't assume it's whatever directory you're in, and don't assume it's one repo, or a repo at all. Tell me what you found before you use it, and if it spans several places say which parts you read. Where there's code you can read, use it: git history, dependencies, CI, README, open issues, incident notes. Where there isn't, ask me. Only ask me the questions marked source:"ask", about five of them. Skip everything marked source:"browser"; I'll tap those in myself, and that includes every price question, so don't raise price at all. For source:"confirm", propose an answer, say what it's based on, and let me correct it. Put what each answer rests on in the evidence object. Short and factual. Leave out anything you're unsure of rather than guessing. Then give me the prefill URL. Don't submit anything.