My recent contract in User Research and Data Quality Assurance marked a turning point. I formalized processes, ensured data accuracy, and created an effective feedback loop between engineering and operations. Through this work, I gradually shifted from reactive problem-solving to something more strategic—architectural thinking. Instead of constantly putting out fires, I began contributing in a systematic and purposeful way.
This shift stands in stark contrast to six years spent in crisis mode, improvising solutions each day. To explain why this evolution matters, I need to revisit where I came from.
The Backstory: Learning Through Challenge
Before QA, I led IT Operations at a small game studio with a 25-year history. As the sole member of my department, I inherited what the Chief Creative Officer described as an old, confusing, and broken set of systems.
During those years, adaptability and resourcefulness weren't luxuries - they were survival. I modernized infrastructure while keeping operations running, and I'm particularly proud of rescuing 20 years of digital assets from failing on-premise servers, managing two full-scale office relocations without any business disruption, and executing a complex BigCommerce migration. That last project required me to programmatically map over 2,000 legacy SKUs and consolidate 16 fragmented subscription types into two unified global options. The result: 80% reduction in subscription errors, PCI compliance, and revenue growth of 10x.
I also designed systems meant to last. A custom digital product catalog I built became the production standard for over six years with minimal maintenance. Custom web solutions. A secure web presence maintained solo. Throughout it all—limited resources, creative solutions, constant adaptation—I developed things that worked.
The Moment Everything Changed
After the company sold its IP, I decommissioned the systems I had built. Many projects went unfinished. The roadmaps I'd developed for platform consolidation and community growth were simply deleted, no longer needed in the new context.
I won't pretend that didn't sting. But it clarified something essential: I'm ready to move beyond firefighting. I'm ready to design robust, enduring systems that will last.
The Path Forward
My years in Operations and QA taught me the value of adaptability and the power of simple, effective processes. Building on that foundation, I'm now focused on mastering the fundamentals of Computer Science to deepen my technical expertise and broaden my problem-solving toolkit.
Looking ahead to 2026 and beyond, my ambition is clear: design scalable tools, expand my systems knowledge, and enhance data security across every project I touch. I'm committed to creating robust architectures, streamlining workflows, and implementing reliable solutions that prevent problems before they arise.
I'm energized by the possibilities of this next chapter. I'm eager to make a lasting impact by developing innovative, resilient solutions that empower teams, drive progress, and define my legacy through architectural excellence.
Not firefighting. Building.