Chapter 2 of 2
Every Bug Taught Me Something New
The most valuable lessons in programming often come from the mistakes we spend hours trying to fix.

Tap the picture to see it full size
As I started building more projects, I noticed a pattern.
The excitement of creating something new was always followed by a moment when nothing seemed to work. Sometimes the application wouldn't run. Other times, a small change would unexpectedly break another part of the project.
My first reaction was always frustration.
I would read the same error message over and over, hoping the solution would somehow appear. More often than not, it didn't.
Instead, I learned to slow down.
I began reading documentation more carefully, testing one change at a time, and understanding what the error was actually trying to tell me. Instead of treating debugging as a roadblock, I started seeing it as an investigation.
Every solved bug gave me more than a working program.
It taught me how to think logically, stay patient under pressure, and approach problems with curiosity instead of panic.
Looking back, I realize that the hours spent debugging weren't wasted time.
They were the moments that transformed me from someone who simply wrote code into someone who truly understood how software works.
Written by
Prachi LohkareA student trying to balance code, curiosity, and life. I write about growth, self-discovery, and the lessons that come from building things and making mistakes.
More by Prachi Lohkare
Short link: hurroz.com/c/ENTC3
i really liked the shift from frustration to curiosity it felt authentic and showed how growth comes from changing your mindset rather than avoiding difficult moments
I actually like debugging...there was once when I kept debugging for 2 while days...the bug was not fixed no matter how much time I try...and then I cleared it finnally and the satisfaction I got when I executed my projects was worth everything