Learn automation with bounded, rerunnable jobs

Your starting point

You have a project folder and can run a short script. Work on files created specifically for the exercise.

• Conditions, loops, functions, and file paths
• A disposable fixture directory inside the project

Your finish line

You can explain a script’s target boundary, inspect its effects, handle failure, and rerun work without silently duplicating it.

Stack up four small wins

1. STEP 1 OF 4

   Define the boundary before the loop

   Make a small fixture folder with ordinary files, an empty file, and a filename containing spaces.

   Bro tip: Write down the allowed input and output folders, then inspect the selected file list. Include the filename with spaces in that check.

   What you’ll learn

   • Working directories
   • Resolved paths
   • Inputs versus generated output
   You’re ready to move on when

   The script identifies only the intended fixture files and excludes its output directory.

   I can do this step

2. STEP 2 OF 4

   Preview a file operation

   Build the fixture organizer with a preview-first workflow.

   Bro tip: Compare the preview with the fixture folder before applying it. Afterward, inspect the actual destinations against that same plan.

   What you’ll learn

   • Dry runs
   • Collision rules
   • Deterministic plans
   You’re ready to move on when

   The dry run changes nothing and the apply result matches the inspected plan.

   Open project: Fixture file organizer

   I can do this step

3. STEP 3 OF 4

   Transform a batch with an audit trail

   Convert sample CSV files to JSON while preserving rejected-file details.

   Bro tip: Put a valid file and a malformed file in the same sample batch. Follow both outcomes into the final summary.

   What you’ll learn

   • Per-file validation
   • Structured summaries
   • Exit behavior
   You’re ready to move on when

   Accepted, rejected, and skipped files are all listed, and invalid input cannot masquerade as success.

   Open project: Audited batch converter

   I can do this step

4. STEP 4 OF 4

   Recover work after interruption

   Build a local job runner using harmless file-output tasks and simulated failures.

   Bro tip: Pick one planned interruption point and record the job state before restarting. Compare the final files with the uninterrupted fixture run.

   What you’ll learn

   • Job identity
   • Checkpoints
   • Bounded retries
   You’re ready to move on when

   Restarting after interruption completes each intended result once under the documented policy.

   Open project: Recoverable local job runner

   I can do this step

Your build lineup

1. Fixture file organizer

   Preview and apply a small file-copy plan inside a disposable exercise folder.

2. Audited batch converter

   Convert several sample CSV files to JSON while reporting each success, skip, and rejection.

3. Recoverable local job runner

   Run harmless predefined file-output jobs, record attempts, and resume after a simulated interruption.

Watch it. Then build it.

Start with a worked example, then connect the recording to your own small, checkable build. Videos open on their creator’s or publisher’s website.

Read Vibe Bro’s written lesson briefing ↗

1. Beginner · Video

   Demo: Managing the file system | More Python for Beginners [13 of 20]

   Microsoft Learn · More Python for Beginners

   A short Python demonstration of listing files and folders in the local filesystem.

   For step 1: Define the boundary before the loop

   Before watching: Python variables, loops, and imports; a small disposable fixture directory inside your project.

   Watch, then try

   List only the disposable fixture directory. Display the resolved root, identify files separately from folders, and exclude the generated-output directory before planning an organizer operation.

   This lesson supports the inventory stage. Add the starter's preview, collision policy, and plan-versus-apply checks before changing files. Translate the idea into your project's language when it uses a different stack.

   Watch video ↗ · Practice: Fixture file organizer

2. Next step · Video

   CS50P - Lecture 6 - File I/O

   Harvard CS50 · David J. Malan

   Introduces reading and writing files, context managers, and CSV records through small Python programs.

   For step 3: Transform a batch with an audit trail

   Before watching: Python functions, loops, lists, dictionaries, and basic exception handling. Earlier CS50P weeks supply this background.

   Watch, then try

   Follow the file-opening and CSV sections with fictional inputs. Use a proper CSV reader, preserve the source, and add a rejected-input report when adapting the ideas to the batch converter.

   The lecture teaches Python file I/O. Our starter adds JSON output, per-file accounting, and explicit failure status. Keep all practice writes inside the fixture workspace.

   Watch video ↗ · Practice: Audited batch converter

   Publisher’s course details · checked October 28, 2026

Video links selected October 28, 2026. Selection checks cover publisher metadata and topic fit.

The docs behind it

These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.

• Python — CSV dialects and parsing
• Python — Path resolution, globbing, and file operations
• Python — Synchronized bounded queues

Documentation links checked October 27, 2026.

Keep the momentum going

• Automate a bounded file operationCopyable prompt
• Dead letter queueCoding term
• Dry runCoding term