CS STUDENT // LOVE OF THE GAME // NONCHALANT
19 year old CS student. I spend most of my time writing low-level code, breaking things apart to understand them, and building stuff that actually works.
01.
I'm 19, studying computer science, and I've been building things since I was a kid.
My focus is software that operates close to the metal. I enjoy reverse engineering, native tooling, and figuring out how systems tick at a level most people don't bother with. I'm not interested in surface-level stuff — I want to understand exactly what's happening and why and how to manipulate it of course.
When I'm not on personal projects I'm studying full-time — grinding through algorithms, OS theory, and the kind of CS concepts that actually make you a better programmer [sometimes].
02.
Inverse X was a community I built and ran from scratch. We developed and sold custom game cheats and hardware ID spoofers — software that required real knowledge of anti-cheat internals, Windows kernel structures, and driver-level memory manipulation.
Scaling it to 11k active members meant building out the full backend myself — license auth, product delivery pipelines, and keeping everything stable under constant load. No budget, no team, just figuring it out.
Honestly the thing that taught me more than most of my formal education. Real traffic, real problems, real consequences if something broke.
FCAT is a file analysis tool I built — think VirusTotal but written by me, for learning and actual use. You drop in a file and it runs a full breakdown: PE header parsing, section analysis, string extraction, import table inspection, and entropy checks to flag packed or obfuscated binaries.
The whole analysis runs client-side in the browser — no file ever leaves your machine. Built it to get hands-on with PE internals and understand exactly what static analysis tools are actually doing under the hood. It's the kind of project that forces you to read specs and figure stuff out, not just follow a tutorial.
A 2D tile-based adventure game built to solidify OOP principles — not because games are easy, but because they force you to think in systems. Entities, inheritance, polymorphism, collision handling, a simple event loop — all of it has to fit together cleanly or nothing works.
Wrote versions in both Python (using Pygame) and Java (Swing), which was a useful exercise in seeing how the same architecture feels in two completely different languages. The Java version ended up being a lot more verbose but also made the class hierarchy feel more explicit and intentional.
A bunch of smaller things built along the way to actually learn, not just read about things. A Python CLI task manager with file persistence. A Java banking simulator covering encapsulation, interfaces, and exception handling properly. A Python graph visualiser for Dijkstra's algorithm I built when I kept forgetting how it actually worked. A port scanner written in Python that taught me more about sockets and networking than any lecture did.
None of these are impressive on their own, but building them is the difference between understanding something and just knowing what it's called.
03.
Languages I actually use day to day — not just listed for the sake of it.
04.
I'm going to start writing about the things I actually know — not tutorial rehashes, just what I've learnt the hard way. Topics like getting past the "hello world" phase in C#, why C++ is hard and why that's the point, and what it actually looks like to build real things.
Not another beginner guide. This covers the stuff that trips people up once they leave the basics behind.
Coming SoonMemory, pointers, undefined behaviour — and why learning all of it makes you a better programmer in every language.
Coming SoonIf you already know another language, here's how to pick up Python without wasting time on the obvious stuff.
Coming SoonLess about Spring and enterprise, more about what Java actually teaches you about OOP and typing systems.
Coming Soon05.
If you want to work on something or just think I'm worth talking to, reach out.