From Gaming Curiosity to Cloud and DevOps

I have always enjoyed playing games. Growing up, however, I never had a system powerful enough to run high-end titles like GTA V. At the time, I wanted to experience those games badly, but hardware limitations made it impossible.

That curiosity eventually led me to explore cloud gaming. The idea itself felt exciting — powerful hardware somewhere else, streamed directly to my screen. But the experience was far from perfect. There were long waiting times, frequent frame drops, and noticeable lag.

Instead of accepting it as a limitation, I found myself asking a simple question: why does this happen?

While researching cloud gaming performance, I learned about one of the most fundamental challenges in distributed systems: latency.

Concepts like network distance, shared infrastructure, congestion, and resource contention helped explain why performance could vary so drastically. What fascinated me was not just the technology itself, but the realization that performance issues were often the result of system-level decisions, not individual bugs.

The deeper I went, the more curious I became about how large-scale systems are designed, operated, and optimized. What started as a gaming problem slowly evolved into an interest in cloud architecture, reliability, and performance engineering.

While searching for a summer internship later on, I was introduced to DevOps. Learning about DevOps shifted my perspective — it wasn’t just about automation or tools, but about ownership, reliability, and understanding the impact of changes on real systems.

With nearly a year of hands-on experience working in production environments, my understanding of DevOps has matured significantly. Real systems teach lessons that tutorials cannot.

Looking back, it’s interesting how a simple desire to play a game led me toward cloud computing and DevOps. What began as frustration with performance turned into curiosity, and that curiosity gradually shaped my career path.

I’m still learning every day, but one thing has remained constant: asking why.