You built a working system through AI and cannot yet read it. This school fixes that, in short lessons, on your own scripts, with every claim checked by running it on the Dell.
The rule that keeps hallucination out
Nothing on this site asks you to take my word. Every lesson ends in something you run. If what the screen prints does not match what the lesson said, the lesson is wrong and you tell me. Outside exams, graded by people and software that are not me, are the final check.
Each lesson is 10 to 15 minutes and follows the same five beats. The order comes from PRIMM, a method from computing education research built on one finding: people learn to code faster when they read and predict before they write.
Fun, but not a toy: each session ends with a broken copy of one of your scripts. You fix it. That is the test.
The charter you wrote, with one session added at the front. About 12 hours.
| Session | You learn it on | After it you can |
|---|---|---|
| 0. The terminal | PowerShell on the Dell | Move around folders and run a script without a paste from me |
| 1. How to read code | snapscan-sync | Name every part of any file |
| 2. Python, enough to read | scribe-delivery, drive-index | Explain out loud what a module does |
| 3. Debugging | Broken copies of both | Read an error, find the line, try a fix |
| 4. Git, the safety net | test-git in GitHub Desktop | See what changed and undo it |
| 5. JavaScript literacy | The weisspress Worker | Read the file that routes every weiss.press page |
| 6. Regex and a strange repo | sms-feed patterns, one of your forks | Size up code someone else wrote |
| 7. Capstone | One thing that annoys you | Fix your live system yourself |
This is the part that makes it legitimate. I cannot certify you and a certificate from this site would mean nothing. These three can, in this order:
| Credential | Who grades it | Why this one |
|---|---|---|
| Harvard CS50P | Harvard's automatic checker | Free certificate. You must write code that passes their tests. |
| GitHub Foundations | Proctored exam | Written for project managers as well as developers. Fits a PMP. |
| PCEP | Proctored exam, 30 questions | The standard entry-level Python certificate. |
Track 1 gets you reading. Track 2 is where you prove it to someone who is not us.
You said you do not know what you do not know. This is the list. What you have today is scripts: one user, one PC, files in Drive. A product other firms pay for needs eight things your scripts do not have. You do not need to code them. You need to know them well enough to direct the build and judge the result.
| Topic | The plain question it answers | Where you already touch it |
|---|---|---|
| Data model | What are the things (project, submittal, RFI, invoice) and how do they connect? | Your Sheets and CSV indexes |
| Database and SQL | Where does it live so two people can use it at once? | sms-search already uses SQLite |
| API, HTTP and JSON | How do two programs talk? | Todoist, Fireflies and Gemini calls in your modules |
| Front end and back end | What runs in the browser, what runs on the server? | The weisspress Worker |
| Accounts and tenants | How does client A never see client B? | Not yet. This is the big new one. |
| Tests | How do you know a change did not break something? | Every module's --check |
| Environments and deploy | How does a change get from a draft to live, safely? | Push to main, Cloudflare builds |
| Security and secrets | Where do keys live and who can read what? | Your key files and environment variables |
Running through all eight: writing a spec. With AI building, the scarce skill is saying exactly what you want and checking you got it. That is procurement and project management. You already do it for buildings.
Session 1 ● 12 minutes ● Phone is fine
The file is modules/snapscan-sync/run.py. You know what it is for: it copies new scans from the scanner folder to the Tailscale folder and to Drive. Now see how it is laid out. The line numbers match the real file.
Part A. The note at the top. Three quote marks open it, three close it. Python ignores it. It is for people.
1"""
2snapscan_sync v1, 2026-10-07
3Copies new scans from the scanner's local folder to the Tailscale folder and to Google Drive.
11Copy only. It never deletes, moves or renames anything, on the PC or in Drive.
18"""
Part B. Imports. Tools borrowed from Python's own toolbox.
19import os
20import shutil
21import subprocess
22import sys
23from datetime import datetime
24from pathlib import Path
Part C. Settings. Names in capitals, set once at the top. This is where you would change a folder.
26VERSION = "snapscan_sync v1.0 2026-10-07"
29SOURCE = str(Path.home() / "snapscan 2026")
30MIRROR = r"D:\TAILSCALE FOLDER\snapscan 2026"
34MIN_AGE = "1m"
35EXCLUDE = ["*.tmp", "~$*", "Thumbs.db", "desktop.ini"]
Part D. Functions. Each def is one named job. This file has five: log, find_remote, copy, report, main.
46def log(msg):
47 line = f"{datetime.now():%Y-%m-%d %H:%M:%S} {msg}"
48 print(line)
49 with open(LOG, "a", encoding="utf-8") as f:
50 f.write(line + "\n")
Part E. The start button. The last lines of the file. Nothing above them runs until this says go.
136if __name__ == "__main__":
137 try:
138 sys.exit(main())
log, the script does two things with the same line of text. What are they?"a" on line 49 means append.main, lines 113 to 121: if the folder's parent is not there, the script logs a WARN line and skips that copy. Finding where a name is used is the core reading move. You will do it a hundred times.MIN_AGE = "1m" becomes "5m". You just located a change without reading the other 140 lines.You can now
Open a Python file and point to its five regions: the note, the imports, the settings, the functions, the start button.
Session 1 ● 10 minutes ● At the Dell
This script has a safe mode. Read these lines from main:
102 dry = "--dry-run" in sys.argv[1:]
108 if dry:
109 print(f"{VERSION} DRY RUN, nothing is copied")
And this, from report:
88 if not files:
89 if dry:
90 print(f"{label}: nothing new")
91 return
If you run the script with --dry-run and there are no new scans, what exactly is the first line it prints?
On the Dell, open PowerShell and paste this one line. It copies nothing.
C:\Users\rob\AppData\Local\Python\pythoncore-3.14-64\python.exe C:\Users\rob\Documents\GitHub\test-git\modules\snapscan-sync\run.py --dry-run
The first line should read exactly:
snapscan_sync v1.0 2026-10-07 DRY RUN, nothing is copied
The {VERSION} in line 109 was swapped for the text on line 26. That swap is what the f before the quote mark does.
After it, one line for the Tailscale folder and one for Google Drive. Each says nothing new, or WOULD COPY and a list of files if a scan is waiting.
If you saw something else, send me the screen. Either the lesson is wrong or you found a real problem. Both are worth knowing.
You can now
Read a line of code, say what it will print, and check yourself against the machine.
Session 1 ● 15 minutes ● At the Dell
You never practice on the live copy. The Dell's scheduled tasks run that folder. Make a practice copy first. Paste these two lines in PowerShell:
mkdir C:\Users\rob\Documents\CODE_SCHOOL\lesson1
copy C:\Users\rob\Documents\GitHub\test-git\modules\snapscan-sync\run.py C:\Users\rob\Documents\CODE_SCHOOL\lesson1\run.py
Open the practice file in Notepad:
notepad C:\Users\rob\Documents\CODE_SCHOOL\lesson1\run.py
DRY RUN, nothing is copied to PRACTICE RUN by Rob. Keep the quote marks. Save.C:\Users\rob\AppData\Local\Python\pythoncore-3.14-64\python.exe C:\Users\rob\Documents\CODE_SCHOOL\lesson1\run.py --dry-runAn error ending in a line that starts with SyntaxError, with line 109 a few lines above it and a mark under the place Python got confused. The exact wording varies by Python version. The two facts that matter are always there: the kind of error, and the line.
Put the quote mark back. Run again. It works. You have just done the whole debugging loop once: read the error, find the line, fix one thing, run again. Session 3 is two hours of exactly this, on harder breaks.
You can now
Change a script, run it, break it, read the error and repair it, without opening a chat.
Say these out loud to the Plaud, or type them. I grade them against the file, not against my memory.
--dry-run change, and which line reads it?Primary sources only. Each one is linked so you can check it.