She Used to Delete Everything She Got Wrong. Here Is What Changed.

Nadia was six weeks into an online coding course when she started keeping a mistake log. Not because someone told her to. Because she got tired of making the same errors and not knowing why.

What the old pattern looked like

Before the log, every error message felt personal. She would fix the bug, delete the broken version, and move on. The problem was that she kept hitting similar walls. Fixing without understanding meant the same confusion came back in a slightly different shape two lessons later.

The deletion habit was not laziness. It was discomfort avoidance. Looking at a broken piece of code felt like looking at proof she did not belong in the course.

The log changed the relationship with errors

After she started writing down each mistake, what caused it, and how she resolved it, something shifted. The log turned errors into data rather than verdicts. By week nine, she could scan her notes and spot a pattern: she consistently misread variable scope. That single insight saved her hours.

The before state was: error appears, panic, fix fast, forget. The after state was: error appears, note it, understand it, reference it later.

This is a small process change, not a personality overhaul. It does not require motivation or confidence. It just requires a text file and two minutes after each session. The mindset shift followed the habit, not the other way around. That sequence matters for beginners because waiting to feel confident before changing behaviour is usually what keeps the old pattern locked in place.