Engineering Notes
From Gaming Curiosity to Cloud and DevOps
How a simple question about gaming performance and latency slowly shaped my interest in cloud systems, infrastructure engineering, 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, noticeable lag, and inconsistent performance.
Instead of accepting it as a limitation, I found myself asking a simple question:
Why does this happen?
While researching cloud gaming performance, I encountered one of the most fundamental ideas in distributed systems: latency.
Concepts like network distance, congestion, shared infrastructure, and resource contention helped explain why performance could vary so drastically. What fascinated me most was realizing that performance problems were often the result of system-level trade-offs rather than isolated bugs.
The deeper I explored, the more curious I became about how large-scale systems are designed, deployed, and optimized. What started as a gaming problem slowly evolved into an interest in cloud architecture, infrastructure reliability, and performance engineering.
Discovering DevOps
Later, while searching for internship opportunities, I was introduced to DevOps. Learning about DevOps changed how I viewed software systems entirely.
It wasn’t just about automation tools or deployment pipelines. It was about ownership, reliability, operational thinking, and understanding how changes impact real systems in production environments.
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 and certifications simply cannot.
Systems Thinking
Alongside cloud engineering, my ICT background exposed me to operating systems, networking, and digital logic. Designing a CPU in Logisim was especially eye-opening because it demonstrated how software behavior ultimately emerges from low-level hardware decisions.
That systems perspective now shapes how I think about cloud infrastructure, automation, scalability, and reliability engineering.
Looking Back
Looking back, it’s interesting how a simple desire to play a game led me toward cloud computing and DevOps.
What started as frustration with performance slowly became curiosity — and that curiosity eventually shaped my career direction.
I’m still learning every day, but one thing has remained constant:
Keep asking why.
More Writing Coming Soon
Upcoming articles will focus on Terraform deployment systems, AWS automation tooling, ECS blue-green deployments, and infrastructure reliability engineering.