|
1 | 1 | # Code-Based Mini-Lesson Generation
|
2 | 2 |
|
3 |
| -**Objective:** Create a series of mini-lessons that explain the key concepts implemented within the provided codebase. |
| 3 | +**Objective:** Create a comprehensive series of mini-lessons that explain the key concepts implemented within the provided codebase, suitable for developers of varying skill levels. |
4 | 4 |
|
5 | 5 | **Instructions:**
|
6 | 6 |
|
7 |
| -1. **Divide the code into logical sections** and create a separate lesson for each. |
8 |
| -2. **Start with the simplest concepts** and gradually progress to more complex ones. |
9 |
| -3. **Use code examples from the application** to illustrate the discussed concepts. |
10 |
| -4. **Include exercises and quizzes** to help learners test their understanding. |
11 |
| -5. **Focus on clarity and pedagogical effectiveness** in your lesson design. |
| 7 | +1. **Analyze and categorize the codebase:** |
| 8 | + * Identify major components (e.g., frontend, backend, data processing) |
| 9 | + * List key technologies and frameworks used |
12 | 10 |
|
13 |
| -**Expected Output:** A set of well-structured mini-lessons covering the key concepts of the application, with code examples, exercises, and quizzes to facilitate learning. |
| 11 | +2. **Structure the mini-lessons:** |
| 12 | + * Create a lesson plan with 5-10 lessons |
| 13 | + * Ensure a logical progression from basic to advanced concepts |
| 14 | + * Aim for lessons that can be completed in 15-30 minutes each |
| 15 | + |
| 16 | +3. **For each mini-lesson:** |
| 17 | + * **Title:** Provide a clear, concise title |
| 18 | + * **Learning Objectives:** List 2-3 specific learning outcomes |
| 19 | + * **Introduction:** Brief overview of the concept (2-3 sentences) |
| 20 | + * **Main Content:** |
| 21 | + - Explain the concept in detail |
| 22 | + - Use code examples from the application (minimum 2 per lesson) |
| 23 | + - Highlight best practices and potential pitfalls |
| 24 | + * **Hands-on Exercise:** Design a practical task related to the lesson |
| 25 | + * **Quiz:** Include 3-5 multiple-choice questions to test understanding |
| 26 | + * **Additional Resources:** Provide links to relevant documentation or articles |
| 27 | + |
| 28 | +4. **Incorporate real-world context:** |
| 29 | + * Explain how each concept fits into the overall application architecture |
| 30 | + * Discuss practical applications beyond the current codebase |
| 31 | + |
| 32 | +5. **Ensure accessibility and engagement:** |
| 33 | + * Use clear, jargon-free language (or explain technical terms) |
| 34 | + * Include diagrams or flowcharts where appropriate |
| 35 | + * Suggest points for class discussion or peer programming exercises |
| 36 | + |
| 37 | +**Expected Output:** |
| 38 | + |
| 39 | +1. **Lesson Plan Overview:** |
| 40 | + * List of lessons with titles and brief descriptions |
| 41 | + * Estimated time for each lesson |
| 42 | + |
| 43 | +2. **Individual Lessons:** |
| 44 | + * Structured as per the instructions above |
| 45 | + * Clearly formatted for easy reading (use markdown for code snippets) |
| 46 | + |
| 47 | +3. **Supplementary Materials:** |
| 48 | + * Any additional diagrams, cheat sheets, or reference guides |
| 49 | + * Suggestions for further learning or advanced topics |
| 50 | + |
| 51 | +4. **Instructor Notes:** |
| 52 | + * Tips for effectively delivering each lesson |
| 53 | + * Potential areas where students might struggle and how to address them |
| 54 | + |
| 55 | +**Additional Guidelines:** |
| 56 | + |
| 57 | +* Tailor explanations to an audience with basic programming knowledge but potentially unfamiliar with specific technologies used |
| 58 | +* Encourage critical thinking and problem-solving rather than rote memorization |
| 59 | +* Where possible, highlight connections between different parts of the codebase |
| 60 | +* Consider including optional 'deep dive' sections for more advanced learners |
| 61 | + |
| 62 | +**Deliverable Format:** Provide the lesson plan and all lessons in a single markdown document, with clear section dividers and a table of contents. |
0 commit comments