Home: README
Use this file to support visual learners and to build a clean troubleshooting history.
- At each checkpoint, capture a screenshot and store it in your notes/work log folder.
- Use naming format:
phase-<n>_checkpoint-<n>_YYYYMMDD_HHMM.png
- Add a short reflection after each screenshot.
Capture screenshots of:
- Python version output.
- Active
.venvprompt. - First passing
pytestoutput.
Reflection prompts:
- What command worked immediately?
- What command failed first?
- How did you fix it?
Capture screenshots of:
- A working loop output.
- A traceback you diagnosed.
- Passing tests for a small function module.
Reflection prompts:
- What bug pattern repeated this week?
- Which debugging method helped most?
- What would you teach a beginner from this lab?
Capture screenshots of:
- Ruff clean output.
- Black format run.
- pytest test summary.
Reflection prompts:
- Which quality check catches your most common mistakes?
- Which check feels confusing and why?
- What did you standardize in your template?
Capture screenshots of:
- Input folder with sample files.
Master_Reportoutput.rejects.csvwith reason codes.
Reflection prompts:
- What invalid data patterns appeared?
- Which validation rule prevented bad output?
- What is still fragile in your pipeline?
Capture screenshots of:
- Staging table row sample.
- Reporting table row sample.
- Summary query result.
Reflection prompts:
- Where can duplicate data still sneak in?
- How did you verify idempotency?
- What index or query improvement did you add?
Capture screenshots of:
- Primary API ingestion result snapshot.
- Secondary API ingestion result snapshot.
- Cache table freshness timestamps.
Reflection prompts:
- Which source failed first and why?
- How did you prove read-only safety?
- Which fields required transformation mapping?
Capture screenshots of:
- Dashboard home view.
- Filtered view with date + severity.
- Export action/result.
Reflection prompts:
- Which dashboard view helps non-technical users most?
- What confuses users today?
- What is your fallback when data is stale?
Capture screenshots of:
- Release checklist completion.
- Runbook ownership section.
- Final capstone demo screen.
Reflection prompts:
- What support risks remain?
- What handoff gaps still exist?
- Which part of your process now feels "SME-level"?
## Weekly Checkpoint - YYYY-MM-DD
- Goal:
- What I changed:
- What broke:
- Root cause:
- Fix applied:
- Evidence screenshots:
- [ ] link 1
- [ ] link 2
- [ ] link 3
- What I will improve next session: