It was just another ordinary day at the helpdesk, when a ticket landed in the queue that instantly made the team exchange glances that said, “You’re not going to believe this one.” The user simply described their “computer not working” issue. Nothing unusual so far, right? Then the details came through.
According to the user, their computer had suddenly stopped responding. Naturally, they tried the usual – pressing buttons, unplugging and re-plugging cables, hoping for a miracle. When those attempts failed, they did what they thought was a “logical next step.” They poured water on the machine.
Yes, you read that correctly—water. The user explained they had heard somewhere that water could “cool down overheating parts,” and since the computer was clearly giving no signs of life, they assumed it might have overheated. The aftermath? Complete silence from the computer, the power light flickering like a doomed firefly, and a follow-up desperate plea sent to IT: “Please fix ASAP, my water-cooled PC is now totally dead!”
When the helpdesk technician called the user to clarify, the conversation was equal parts baffling and funny. The user confessed proudly, “Well, I figured a little water couldn’t hurt—computers need water to grow, right? Like plants. So I just gave it a little watering.”
After a careful and extremely gentle explanation that computers don’t thrive on hydration, the tech reluctantly marked the ticket as “hardware damage due to liquid exposure.” It was a tough day for empathy, but the whole team took a moment to remind themselves that sometimes, what seems obvious to IT folks can be a complete mystery to the untrained user.
The moral of the story? When your computer acts up, maybe hold off on watering it and call your friendly helpdesk first. They might save you a brilliant “gardening” experiment—and your poor machine.