The Architect behind notamitgamer

Philosophy & Background

I started writing code five years ago, and I never really got into the whole "chase the newest framework" thing - I got more obsessed with understanding what's actually happening underneath, mostly because "it works on my machine" bit me in the ass one too many times and I decided that wasn't a real answer. C was the obvious starting point: I wanted to know how memory actually gets allocated, how pointers find their way around hardware, and how a program talks to an OS without just trusting that it works - and nothing humbles you faster than a segfault with zero stack trace and zero explanation.

Today, as a B.Sc. Computer Science student, I am actively working to bridge the gap between that low-level systems architecture and modern high-level interfaces like AI and web platforms. I don't just want to consume an API; I want to understand how the server routes the request, how the data is encrypted in transit, and how to sandbox the execution environment - call it trust issues, but for computers.

• The Long Game: Code quality is a reputation currency. I consciously avoid premature freelancing because my current focus is pure mastery - building distributed systems, writing C that outlives its author, and creating infrastructure robust enough for the real world (and my future 3am debugging sessions).
• Problem > Syntax: I architect solutions to my own friction. Whether it's securely encrypting source code to prevent theft or building a CLI to test scripts without cloning repos, every tool I build starts as a direct solution to a bottleneck I faced personally - I'm basically my own most annoying client.

Architecture Labs

The projects from the homepage, minus the marketing gloss - what they actually do under the hood, for the three people who scroll past the emoji and want the technical fine print.

Engineering Journals

The start-to-finish write-ups - the friction that caused each project, the architectural decisions, and where things went sideways before they worked.

Unlike this page, these are written in complete sentences, with actual paragraph structure, like a person who owns a semicolon and knows what to do with it.

Environment Config

Engineered for deterministic performance and minimized thermal throttling, calibrated to reduce overhead during heavy LLVM/GCC compilation cycles. Basically, a very expensive space heater that occasionally compiles C.

• Compute Core: Intel i5-12400F (6C/12T) - optimized for parallelized multi-threaded compilation and branch prediction efficiency, and for making the fans sound like a small aircraft.
• Mainboard: Gigabyte H610M S2 - unremarkable in the best possible way.
• Memory: 16GB Corsair 3200MHz - enough for Chrome to eat half of it and still ask for more.
• Thermal Solution: Ant Esports Cabinet - strategic airflow to prevent frequency scaling during I/O-heavy workloads, and to prevent me from accidentally forging a katana.

Journey

A greatest-hits timeline, condensed, because nobody needs a full autobiography of my Git commit history.

2026 - Veyrix IDE, WhatsApp Logger, Knowledge Graph verification on Google Search (I'm now an "Official Entity," whatever that means), NCT Legacy archive, Githrun CLI, and Mojic's 256-bit rolling cipher.

2025 - ESAL License, Ada AI's first release, the B.Sc coursework repo, Cloud Compiler API, Adpkg on PyPi, and the original NCT tool. A whole year of pretending I had a plan.

Misc & Open Source

Libraries, coursework, and other side quests I built instead of doing Sem 2 Prep.

Contact

I promise I respond faster than I fix bugs. Email or LinkedIn, your pick.

GitHub. Mostly green squares and regret.