context issues

context.html

<table>
  <thead>
    <tr>
      <th>Mistake</th>
      <th>Description</th>
      <th>Suggested Fix</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>1. Jumping between tasks without summaries</strong></td>
      <td>Sometimes you switched between different modules (e.g., <code>complaints.php</code> → <code>driver documents</code>) without summarizing the previous context.</td>
      <td>Add a quick checkpoint: “We’ve completed complaints.php. Next, we’ll do driver documents. Here’s what I want to carry forward…”</td>
    </tr>
    <tr>
      <td><strong>2. Not providing file structure upfront</strong></td>
      <td>Some initial prompts lacked folder structures or where files belonged, which caused repeated clarification.</td>
      <td>Use a consistent file structure template when starting a new module.</td>
    </tr>
    <tr>
      <td><strong>3. Assuming context is remembered across threads</strong></td>
      <td>You assumed ChatGPT had memory across different chats or sessions. This caused loss of continuity.</td>
      <td>Always repeat key project context when opening a new thread or start with “Let’s continue the CI4 migration for X module.”</td>
    </tr>
    <tr>
      <td><strong>4. Inconsistent naming</strong></td>
      <td>Sometimes your references to modules varied (e.g., “driver page,” “driver bank,” “bank detail view”), causing minor confusion.</td>
      <td>Stick to consistent module names throughout the conversation.</td>
    </tr>
    <tr>
      <td><strong>5. Asking partial questions</strong></td>
      <td>Sometimes you asked “can this be improved?” or “why not working?” without sharing the exact code or problem.</td>
      <td>Share the specific code snippet or describe what behavior you expected vs. what happened.</td>
    </tr>
    <tr>
      <td><strong>6. Not summarizing changes made</strong></td>
      <td>After trying fixes or code updates, you occasionally skipped confirming what was tested or changed.</td>
      <td>Add short summaries: “I added this filter to controller and view, tested with X and Y — works.”</td>
    </tr>
    <tr>
      <td><strong>7. Delaying confirmation of completed tasks</strong></td>
      <td>Sometimes you didn’t confirm if a task was working or not, making it hard to know when to move forward.</td>
      <td>Just say “Task complete. Let’s proceed to the next item.” — helps maintain flow.</td>
    </tr>
  </tbody>
</table>