This is a submission for the Google I/O Writing Challenge

Hey everyone! 👋

I’m Ch Hima Kartikeya Naidu. I just wrapped up my Class 10 from an ICSE school, and I’m currently gearing up to step into my polytechnic diploma journey here in Andhra Pradesh.
My ultimate dream? To build a career in Cyber Security.

But to fuel my creative side, I'm also a small-scale game developer. I love using storytelling and creativity to craft engaging narratives and build virtual worlds.

Right now, if you ask me where my programming knowledge peaks, I'll proudly tell you it's mastering loops in Java, Python, and C. But while practicing how loops repeat actions to move characters or calculate high scores in games, it sparked a realization: How do these exact same fundamental programming concepts connect to the massive world of information security?

Turned out, you don't need to be an expert penetration tester to start thinking like a security professional. It starts right at line one. Here is my "first-look" at security from the lens of a complete beginner.

1. The Infinite Loop Trap: When Logic Becomes a Vulnerability

In my classes, I learned that loops are amazing for repeating a block of code until a specific condition is met. But what happens if a developer makes a logic error and the loop never stops? It creates an infinite loop that hogs system resources and freezes the application.
In the security world, this connects directly to a Denial of Service (DoS) vulnerability. If an attacker finds an unexpected way to intentionally trigger that infinite loop on a web server, they can crash the entire system.

• My Lesson: Secure coding isn't advanced math; it starts with ensuring your loops always have a foolproof, airtight exit strategy.

2. Game Exploits vs. Data Tampering

As a small-scale game dev, I quickly noticed how easy it is to make mistakes with variables. If you don't protect them, a player can open a simple memory-editing tool and instantly modify their health or coins from 10 to 9999.
In the cyber security ecosystem, this is a brilliant parallel to data tampering. Reading through developer safety documentation taught me a fundamental rule of information security: Never trust the client side blindly.

• My Lesson: Whether you are building an indie game or a secure web application, you must always validate user data on the secure server side before your code processes it.

3. C Language and the Reality of Memory Safety

Learning C has been a massive eye-opener for me because it forces you to manage memory manually. Reading up on the tech industry, I realized that a shocking number of history-making cyberattacks happened because of memory mismanagement in low-level software.

• My Lesson: Learning loops and memory basics in C right now isn't just an academic chore for college—it’s actually the foundational step toward understanding how system-level exploits work.

🎮 Moving Forward: The Secure Developer Mindset
Balancing intense board exams, diploma admissions, and indie game design hasn't been a walk in the park. However, shifting my mindset to look at my code through a "security lens" has made programming twice as exciting.

As I start my diploma, I plan on using modern cloud tools like Google Project IDX to experiment with my code in a secure sandboxed environment. It proves a powerful point: Security isn't a separate phase you add at the end of a project; it belongs to the creator from day one.

I might only know the basics right now, but I am incredibly excited to keep building virtual worlds while learning exactly how to defend the real one.

Over to the Community:
To the seniors, mentors, and experienced developers out there:
What is one basic coding habit you wish you had learned on your very first day to write safer code?
Drop your wisdom and tips in the comments below — I'm ready to learn! 👇