By day, I'm a student competing in research olympiads and cybersecurity contests.
By whenever, I'm:
- Developing custom Linux kernels for mobile devices
- Building IoT solutions that solve real problems
- Competing in CTF competitions
- Writing code that's actually useful
1. Write Code That Works
Not "eventually," not "sometimes" — code should be reliable, predictable,
and maintainable. Cut scope, not quality.
2. Learn By Breaking Things
The best way to understand a system is to break it intentionally, then fix it.
Reading documentation helps, but hands-on experience teaches.
3. Share Knowledge
If I learned it the hard way, someone else doesn't have to. Documentation,
writeups, and open-source contributions benefit the community.
4. Compete, But Don't Compromise
Competition drives excellence. But not at the cost of ethical standards or
community trust.
- Gaming: Zenless Zone Zero, Wuthering Waves, Roblox (casual)
- Networking: Building communities (Discord)
- Learning: Statistics, mathematics, networking theory
- Teaching: Mentoring younger developers in security & systems programming
- Bringing Aqua Safe Monitor to competition stage (OPSI 2026)
- Optimizing Phrolova Kernel for stability & performance
- Exploring AI-assisted development workflows
- Contributing to open-source kernel projects
I'm always interested in:
- Collaborating on challenging projects
- Learning from experienced developers
- Contributing to open-source communities
- Exploring new hardware platforms
- Building tools that solve real problems
Feel free to reach out if you share these interests or want to discuss
systems programming, IoT, cybersecurity, or anything technical!