Archive/blog

Debugging Reality: The Truth About Productivity When Exams and Code Collide

Ghanshyam Kanojiya
2 min read·April 13, 2026·7 views
Debugging Reality: The Truth About Productivity When Exams and Code Collide
Certified Asset

Resonance Score: 100% Community Faith

Community Validation

Focus on your studies.”
— everyone

“Just one more feature…”
— Developers

I had exams this week. Real exams. The kind you're supposed to take seriously.

So obviously… I opened my project.


What actually happened

I sat down to study.

Opened my notes. Read one line.

Then suddenly remembered:

  • a bug from 3 days ago

  • a feature idea I had to implement

  • a post I wanted to share on LinkedIn

And just like that… I switched tabs.

The biggest lie

I’ll just code for 10 minutes.”

We all know how this ends.

// expected
study();

// reality
openVSCode();
fixBug();
addNewFeature();
forgetExam();

Productivity report

  • Syllabus completed: 0%

  • Bugs fixed: kind of

  • New features added: unnecessarily many

  • Confidence: questionable

The weird realization

It’s funny how:

  • studying feels like work

  • building feels like flow

Time behaves differently too:

10 minutes of studying = feels like 2 hours

2 hours of coding = feels like 10 minutes

Final thought

Exams will end.
But this random feature I built at 5 AM…
will probably also not matter.

But hey - at least it felt productive.

BONUS: Debugging Reality

It works on my machine.

Famous last words.

Debugging stages

  1. Confidence 😎

  2. Confusion 🤔

  3. Panic 😰

  4. StackOverflow worship 🙏

  5. Acceptance 🧘

Responses

Responses

0 Contributions

Authentication required to participate

The archive is currently silent.