Generate these sections in order (all inside the main-content div):

File basics, paths, modes, seek and tell Theory — Lecture 23

CBSE | XII CS | Computational Thinking and Programming – 2 | 35 min

1. Learning Objectives

[3–5 objectives derived from the exam-importance analysis above (never naming PYQs) — use <ul><li>]

2. 35-Minute Lecture Flow

[HTML table: Time | Activity | Teacher Action — include a concept-based recap/check slot — no PYQ discussion, no PYQ wording anywhere]

3. Concept Notes

[For EVERY sub-concept surfaced by the exam-frequency analysis, never naming or displaying actual board questions: - .def-box for definition with "In exam language: ..." line - .key-box with syntax/rules as <ul><li> - .example-box for worked examples - <pre><code> for code with .kw/.bi/.st/.cm/.nm token spans - .recall-box for output with exact expected output - after each important concept, embed 1–2 self-generated MCQ or Short Answer checks about THIS concept only - every Section 3 check question must hide its answer inside: <details><summary>▶ View Answer</summary>answer/explanation</details> - do not label any question as PYQ, previous year, board-style, PYQ-pattern, or PYQ-style - do not use .pyq-box or .pyq-meta here (in Combined mode .pyq-box is reserved for Section 7) ]

4. Examiner Tricks & Common Mistakes

[Create one .warn-box for each trap from the EXAMINER FINGERPRINT section. Each .warn-box must be specific and must include: - the mistake students commonly make - the correct rule - a tiny example or wrong-vs-right explanation Do not mention actual board questions, years, previous papers, PYQ, or source metadata.]

5. Board Work Plan

[Numbered list: exactly what to write on the blackboard, in order]

6. Classroom Practice Questions

[Self-generated from the examiner-trap patterns analysed above — never call these PYQ-pattern/PYQ-style/board-style. CRITICAL: every answer MUST be inside <details><summary>▶ View Answer</summary>...</details> — never expose the answer directly. 3×1M MCQ + 5×1-2M Short Answer only. Theory lecture restriction: - Do NOT include actual PYQs. - Do NOT include programming/long-answer/HOTS questions in theory lecture practice. - Frame original MCQ/Short Answer questions from exam-frequency concepts and examiner traps only. - Every question must map to one concept/trap discovered in Section 4. MCQ structure: <div class="mcq-box"> <b>Q1.</b> Question text?<br> <ul class="options"> <li>a) ...</li> <li>b) ...</li> <li>c) ...</li> <li>d) ...</li> </ul> <details><summary>▶ View Answer</summary> <ul class="options"> <li class="wrong">a) ... — reason why wrong</li> <li class="correct">b) ... ✓ — reason why correct</li> ... </ul> </details> </div> Short-answer structure: <div class="self-test-box"><b>Q4.</b> Question<br><details><summary>▶ View Answer</summary>Full answer</details></div>]

7. Student Notes (Copy-ready)

[Concise notes — every concept highlighted by the exam-frequency analysis, written purely as concept notes (no PYQ wording) — in .key-box and .def-box; self-check questions in .self-test-box with <details><summary>▶ View Answer</summary>answer</details>]

8. Homework

[DYNAMIC HOMEWORK — match this concept and the question types the board actually uses for it (self-generate the questions; never label them as previous-year or board questions): - 2×1M (MCQ / very-short answer) - 2×2M short answer - 1×3M short answer (or, for a coding topic, a short program / output-prediction question) - You MAY include one 3–5M long-answer or programming question (this concept supports it) Dynamic rule: include a 5M long-answer or a programming question ONLY when this concept is genuinely assessed that way; never force unsupported marks (e.g. a 5M) or question types. same concept — self-generated, never labelled as PYQ-pattern or board-style. Mark difficulty with .critical/.high/.medium tag. EVERY answer wrapped in <details><summary>▶ View Answer</summary>...</details> inside .self-test-box or .mcq-box]

9. Exam Tips

[5 specific tips as .tip-box — derived from examiner traps for THIS topic only — written as plain tips, no PYQ wording]

10. Last-Minute Revision Cards

<div class="card-grid"> [One .card per concept: <div class="card-title">[concept]</div> + 1 rule + 1 example] </div>