Coding Workflows
Notebook Workflows for Exploratory Prompting
Keep experiments tidy: naming, cells, and export paths that survive audits.
Labs-heavy cohort 4 weeks · technical labs BRL 1,320 informational
Responsible facilitator
Caio Andrade
AI instructor for technical learners adopting notebook-first workflows.
Program narrative
Technical learners organize notebook prompts, capture seeds, and export human-readable logs for teammates.
Inside the bundle
- Notebook naming conventions
- Cell-level prompt contracts
- Seed logging without clutter
- Export paths to markdown reports
- Pairing scripts for mentors
- Clean-up drills for messy branches
- Live coding labs
Artifacts you should exit with
- Publish a notebook template repo
- Ship markdown exports mentors can skim
- Reduce duplicate experiments by half
Learner questions
Jupyter and VS Code notebooks; principles apply elsewhere.
Notes from participants
Cell-level contracts stopped the chaos. Clean-up drills felt short—wanted one more week—but exports are finally readable.
Patrícia N. · Data translator
Next step
No instant checkout—send context through the inbox and we reply with seat options in BRL.
Request information