Here is how I’m looking at security as a beginner dev:
1. When Loops Turn Into Security Flaws (Infinite Loops)
In my classes, I learned how to use loops to repeat code until a condition is met. But what happens if a programmer makes a mistake and the loop never stops? It creates an infinite loop that freezes the software. In the security world, if an attacker finds a way to trigger an infinite loop on a server, they can crash the whole system. This is a basic form of a Denial of Service (DoS) vulnerability.
- My Lesson: Writing secure code starts with making sure your loops always have a foolproof exit strategy.
2. Game Exploits vs. Real-World Hacking
As a small-scale game dev, I know that if you don't secure your variables, players can use memory-editing tools to change their in-game currency or health from 10 to 9999. In the cyber security world, this is very similar to a "Buffer Overflow" or memory tampering, where an attacker alters data in a computer's memory to make it do things it shouldn't.
- My Lesson: Whether it's a video game or a secure database, you can never trust what's happening on the client's side without validation.
3. C Language and Memory Safety
Learning C has been eye-opening because it forces you to manage memory yourself. A lot of famous cyberattacks happen because of vulnerabilities in C-based software where memory isn't handled safely.
- My Lesson: Learning loops and memory management in C right now isn't just academic—it's actually the first step to understanding how system-level exploits work.
💡 Final Thoughts:
I might only know the basics right now, but I'm realizing that you don't need to be a master hacker to start thinking about security. It starts with the very first loops and variables we learn in school. I can't wait to level up both my security knowledge and my game dev skills during my diploma!
To the seniors in the community:
What’s a basic coding habit you think every beginner should learn to write safer code from day one?
Let’s hear it! 🚀