From Work Orders to Debugging Code: My Unlikely Path to Computer Science

I have spent the last 20 years solving problems. Sometimes it was a burst pipe, a malfunctioning oven, or a store that needed a quick makeover before an executive walk-through. Now, I solve a different kind of puzzle: debugging JavaScript errors and writing object-oriented programs in Java. It turns out that being resourceful under pressure applies just as much to code as it does to retail emergencies.

This is how my two-decade career in Facilities became the foundation for my transition into Computer Science.

The Beige Computer and Sir Carnit’s Storytime

I was 10 years old at a tech fair in the Philippines when a lady introduced my mom and me to a massive beige desktop computer. She talked about Yahoo and e-commerce like they were going to change the world. In 1996, that sounded so strange my mom laughed it off. (Now she is a full-fledged Amazon shopper, by the way.) But I remember staring at that machine, fascinated, wondering how all that magic fit inside a box. Around the same time, my cousins had PCs at home, and outside of Super Mario, Galaga, and Top Gun on the Famicom, I found myself hooked on Pac-Man, Minesweeper, and Solitaire.

A couple of years later, I took my first Computer class in 6th grade. Except there was not much “computer” involved. Our teacher, Sir Carnit, a young college instructor, decided storytelling was more valuable than teaching us tech. For almost 50 minutes each session, he would share funny anecdotes instead of spreadsheets or coding lessons. We laughed a lot. But did I learn anything about computers? Absolutely not.

Internet Cafés, Markup Languages, and Slow Dial-Ups

It was in high school when things finally clicked. I learned the basics of HTML and CSS, built my first static page, and discovered the thrill of creating something from scratch. I spent hours in internet cafés, battling it out in StarCraft or Counter-Strike, or working on assignments while the dial-up connection crawled like molasses.

Our high school library had a row of computers meant for research, but with the internet taking 45 minutes to connect through Netscape Navigator or Yahoo’s search page, the bell would often ring before we could even look anything up. That forced me to get creative and figure things out offline. It was frustrating, but I think those early limitations taught me how to problem-solve in scrappy ways.

My Curiosity Grew Beyond Classrooms

Beyond school, I was always curious about how things worked. I took apart VHS players and opened up my Sony stereo just to see how the speakers were wired. That obsession extended into gadgets, from switching phones every year (Nokia, Razr, Sidekick, BlackBerry, and finally the iPhone) to tinkering with anything I could get my hands on.

The Career Detour: 20 Years in Facilities and Construction

After high school, I moved to the U.S. and life took over. At 18, I started working in the Construction and Facilities industry for a general contractor. What began as handling simple work orders turned into managing emergencies across retail locations:

• Critical plumbing issues
• Frozen beverage dispensers going offline
• A car crashing into a storefront (more common than you would think)
• Prepping stores for executive visits
• Troubleshooting bakery equipment like malfunctioning ovens

I was on call 24/7. I eventually became an Operations Manager, overseeing dispatch, vendor coordination, cost estimation, and client updates. Looking back, all those years of managing crises, solving problems on the fly, and “debugging” real-world situations became my training ground. They taught me adaptability and resourcefulness — skills I now use when debugging code.

The Coding Bug Bit Hard

Years into my career, I enrolled in a coding bootcamp. It felt like drinking from a firehose — fast, overwhelming, and intense. But despite the burnout, I thrived in troubleshooting mode. Debugging code gave me the same adrenaline rush as solving a late-night facilities emergency. It clicked: problem-solving, whether in a store or inside a code editor, was my common thread.

Finally Owning the Journey

For the longest time, I thought I would be writing stories, not code. Before moving to the U.S., I was a Mass Communication major, dreaming of becoming a journalist. But my first and only job in facilities consumed the years ahead.

At the same time, I avoided math. I was good at arithmetic as a kid but never pushed myself into algebra and beyond. When I chose to pursue Computer Science, it became both a career shift and a personal challenge I could no longer ignore.

Curiosity nudged me forward. I had always tinkered with gadgets and wondered how tech worked behind the scenes. The data helped too. According to the U.S. Bureau of Labor Statistics, jobs in computer and information technology are projected to grow much faster than average between 2023 and 2033, with about 356,700 openings every year as the industry expands.

Today, I am a Computer Science student juggling full-time work, constant modules, and everything life throws at me. My facilities background taught me how to stay calm in high-pressure situations and solve problems quickly. Now, I bring that mindset to debugging code and building projects.

For the first two years of my CS journey, I did not pause to reflect. I was too busy ticking off modules and tackling problems as they came. But now, with 1.5 years left until graduation, I do not want this story to go untold.

That is why I am sharing it now. Because sometimes, the detours we never expected are the ones worth writing about.

So here I am — a debugging enthusiast, a recovering perfectionist, and someone ready to tell the whole story.

Lessons Learned Along the Way

• Problem-solving is a superpower that translates anywhere. Whether coordinating emergency plumbing or oven repairs for large retail stores, or debugging a broken loop in JavaScript, the process is the same: assess, troubleshoot, resolve.
• Resourcefulness is non-negotiable. From slow dial-ups and faulty equipment to cryptic error messages, you learn to work with what you have.
• Your detour is part of your edge. Twenty years in facilities were not wasted. They sharpened my instincts, resilience, and critical thinking.
• Curiosity is my constant. Whether cracking open gadgets as a kid or cracking open code now, it is the same spark that drives me.
• Tech is not just about the latest trends. It is about solving problems, big or small, and that is a language I have been fluent in for decades.