From Report Cards to Crashing Laptops: My Comic IT Journey

60

Report Cards vs. Deadlines

As a teacher, I treated deadlines like sacred things. Report card day was like Judgment Day: no excuses, no extensions, no “we’ll push it to next sprint.” Parents stood outside the classroom like auditors with sharpened pencils, waiting to pounce on any delay. Delivering 50 report cards on time wasn’t just about efficiency —it was survival.Fast forward to IT. Suddenly, deadlines were… negotiable. Project managers would stroll in with a smile and say, “We’ll extend it by two weeks.” Two weeks! I wanted to shout: “If I can deliver 40 report cards with 40 parents glaring at me, I can deliver this user guide without your extensions!” But here’s the twist: project managers don’t glare. They send polite reminder emails, and somehow, those emails are worse. A parent’s glare is sharp, immediate, and over in seconds. A manager’s email sits in your inbox like a passive-aggressive ghost, haunting you until you reply.

The Laptop That Thought It Was Royalty

When I first started working, everyone thought I was “special” because I got a laptop. They joked about it like I’d been handed a crown. In reality, it was less crown and more cursed relic. The screen froze mid-sentence, the mouse vanished like Houdini, and crashes became so routine that backups turned into my daily prayer ritual.My manager even sat down personally to fix the disappearing mouse — a scene that looked less like IT troubleshooting and more like a detective investigating a crime scene. After months of stress, the laptop finally collapsed for good. That’s when my manager sheepishly admitted: “Yeah, that was a faulty laptop. I didn’t expect it to cause so much trouble. You handled it well.” Handled it well? By then, I had practically earned a PhD in patience.

Looking back, I was the unofficial guinea pig in any company I worked in. New laptop? Give it to Sneha. New software? Let Sneha try it. New project running on an unstable environment? Definitely Sneha. The funny part was that I could never tell whether the software was unstable or whether technology simply became nervous in my presence. So many things crashed, froze, and misbehaved that I stopped asking, “What’s wrong with the system?” and started wondering, “Is it me?” Fortunately, those glitches turned me into an excellent tester and an even better observer.

The Mythical Beast Called FrameMaker

Publishing tools were their own comedy show. FrameMaker was the mythical beast I never used in 15 years. Single sourcing? Outsourced to the company’s CMS, thank heavens. But thanks to endless RoboHelp and FrameMaker workshops, when AuthorIT and Content Management System (CMS) arrived, I picked them up so quickly my teammates thought I had superpowers. The truth was simpler: after years of wrestling with tools that refused to cooperate, anything that worked felt like a miracle.

The Button on the Ceiling

Then came the Hyderabad “test.” I was answering a paper but couldn’t submit it. The manager was ready to laugh it off, but I calmly showed her the exact steps I followed. That’s when I spotted the culprit: the Continue/Close button perched smugly at the top of the page. Who looks for a button at the top? It’s like putting the exit door on the ceiling. Naturally, I scrolled to the bottom, where every sane human expects it.When I raised the issue with the documentation manager and the technical expert, they looked at me as if I’d uncovered a cosmic design flaw. I shared my screen, demonstrated my “scroll to the bottom” instinct, and suddenly the expert was alarmed. He thanked me profusely, as though I’d just invented sliced bread.That day, I realized something important: technical writing isn’t just about backend logic or surviving faulty laptops. It’s about noticing the obvious — like “buttons belong at the bottom” and “laptops shouldn’t vanish their mice.”

Discovering UX

A decade later, UX design became popular, and I loved writing for the pages. The flaws on the screen and page UX were obvious to me, and I found it easy — almost natural — to write for UX. What once felt like glitches now became opportunities to shape smoother experiences, and my eye for usability quirks turned into a strength that made writing for design both rewarding and intuitive.

Inbox Avalanches and TGIF Servers

Emails, too, had their quirks. At one point, I thought replying instantly to every email made me efficient. By noon, my inbox looked like a snowstorm. A friend chuckled: “You don’t have to shovel every flake. Just clear the path.” That’s when I discovered filters — suddenly, my inbox wasn’t a blizzard but a neat row of letters waiting politely, like schoolchildren lining up for roll call.And let’s not forget the server that crashed every Friday at 5 PM. I nicknamed it “TGIF.” While others panicked, I treated it like a weekly ritual: restart, coffee, restart again. Eventually, I fixed it permanently. But honestly, I missed the drama. Nothing bonds a team like shared despair over a frozen screen.

The Moral of the Comedy

Looking back, my career wasn’t defined by tools or machines. It was defined by persistence, humor, and the ability to turn everyday glitches into lessons. The faulty laptop taught me resilience, the workshops taught me adaptability, the misplaced button taught me that sometimes the smallest usability tweaks make the biggest difference — and UX design gave me the joy of shaping those lessons into better experiences for others.In the comedy of tools and technology, I found not just glitches but gifts — lessons that continue to shape how I write, notice, and connect.