I Was Just Watching, I Promise

~  Observed, Not Executed  ~

Third year in my college had its own way of teaching lessons—sometimes without a syllabus. One such lesson came from a microprocessor lab, where I learned that even silence can be misinterpreted as noise.

Microprocessor was one subject I respected… and feared. On the day of the practical exam, I genuinely tried my best. Ironically, the programs I avoided studying deeply were exactly the ones that appeared. Our professor, kind enough, allowed us to choose between one easy and one very difficult program. Fate smiled strangely—the difficult one was the hardest topic for me, and the easy one had a twist (we will discuss that in the next blog).

With my mind stuck in a loop, I sat at the bench and started writing without direction—like a processor executing without proper initialization. Everything felt unstable, as if my internal bus was already overloaded.

A small distraction broke my focus. I noticed the student beside me writing confidently, but in a completely different way. Then I saw it—a small bit note. He was copying. At that moment, I wasn’t planning to copy; I was just observing. Curiosity loaded, execution paused.

Somewhere there, my system unknowingly entered a shared bus state.

I didn’t realize that observation itself could trigger a fault. The lab invigilator had been watching us for minutes. When she finally spoke, both of us were scolded—same bench, same warning, same confusion. A perfect Shared Bus Error.

One process executed an illegal instruction. Another process merely stayed connected.
The system flagged both.

The boy looked at me and joked, “Why are you staring at me? You don’t know the program ah?” It wasn’t anger—just friendly debugging. For the rest of the exam, he continued his playful scolding while I returned to my system, now running in high-alert mode, carefully isolating my inputs.

That day, I understood something quietly important. In both systems and life, it’s not always about what you do—it’s about which bus you’re connected to at that moment. Stay too close to a faulty signal, and you might get flagged without ever executing a single wrong line.

Lesson learned the hard way.
Bus connection noted.
Shared Bus Error—never forgotten ⚙️

🤫 “Silence can still look suspicious in a noisy system.”

💡️ Distance reduces false flags.

🖋️ Until next line of code…