Module 5: Data, Files and Automation

Build a useful import/report tool while learning how representations and contracts preserve meaning. This extends Programming Basics from one JSON history into a staged CSV pipeline; it does not repeat terminal navigation or Git setup.

Planning allowance: 14–20 focused hours, included in semester workload. Authored candidate; executable checks do not replace independent review or learner calibration. Full-book reading is not required.

Before you start

Complete the immediate Programming Basics gate: functions, lists/dictionaries, exceptions and files. Delayed retention checks can continue in parallel. Use Launchpad terminal/Git skills to run and review the tool.

Diagnostic: Explain why text "25" and integer 25 behave differently. Trace a dictionary update. Predict what happens when a file read fails. Repair those gaps in Module 0 before writing a larger importer.

Outcomes

• Distinguish text, raw bytes and structured records.
• Parse quoted CSV, reject invalid input and preserve repeated sessions.
• Produce a grouped JSON report without modifying the source.
• Reproduce a run using a raw-byte fingerprint and explicit command.

Concept map

Concept clusters and learning order

Cluster 1: Representation

• Bits, Bytes and Text
• Formats and Schemas

Apply both lessons in Practice 1.

Cluster 2: Data Pipelines

• Parse, Validate and Transform
• Aggregation and Invariants

Apply both lessons in Practice 2.

Cluster 3: Reproducible Tools

• Fingerprints and Provenance
• Command-Line Contracts

Apply both lessons in Practice 3.

Build, review and assess

Use worked examples, guided lab, exercises, case studies and mistake clinic. Finish the independent assessment under the rubric, then consult calibration.

Workload and outputs

Lessons/selected reading 4–6; cluster practice 3–4; implementation and fault checks 5–7; assessment and one bounded repair 2–3: 14–20 hours.

Preserve your implementation, original predictions, actual results, a repaired defect and transfer evidence. Use existing Git/assistance records; keep generated code and copied examples distinguishable from independent work. The common lab archive is downloaded once, but each module implements and verifies a distinct boundary.

Depth and future connection

Reading guide → resources → reference. Capstone throughline explains what to retain. Technical integration specifies prerequisites, evidence reuse and later-semester boundaries.