Philosophy & Background
I wrote my first lines of code five years ago. Since then, my journey hasn't been about rushing to learn the newest frameworks, but rather about understanding the primitives of computing — mostly because I found out the hard way that "it works on my machine" is not a valid architecture. I started with C because I wanted to know exactly how memory is allocated, how pointers navigate hardware, and how a program actually talks to an operating system, and also because nothing humbles you faster than a segfault with no stack trace.
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.
A lightweight, privacy-first PWA code editor that runs fully in-browser. Uses IndexedDB for massive multi-file storage, works offline, supports real-time syntax highlighting, and offers serverless peer-to-peer sharing. Built after one too many "I forgot to bring the assignment" moments.
Offline PWA Editor
IndexedDB Local Storage
Firebase Cloud Links
Read Engineering Journal →
A headless, privacy-first "Companion Device" architecture running 24/7 on Render. It links directly to the WhatsApp Web WebSocket to instantly capture and archive incoming message payloads before "delete-for-everyone" packets can execute. Not spying, just very thorough remembering.
Node.js / Baileys
Render / Uptime-Bot
Cloud Firestore
Read Engineering Journal →
A highly stable bridge between systems programming and modern LLM interfaces. Transitioned from brittle web-scraping into a secure, authenticated Python routing layer powered by the official Gemini API, because apparently I needed a fourth project that month.
Render Server / Auth
Gemini API Router
Firestore Storage
Read Engineering Journal →
A C source code obfuscator built to defeat static analysis. Rebuilt from a weak XOR mask into a memory-hard, 256-bit password-seeded rolling cipher using the Scrypt Key Derivation Function. Turns C code into emojis. Yes, on purpose. No, I don't know why either.
C Standard Lib
Scrypt KDF Engine
Rolling Cipher (256-bit)
Read Engineering Journal →
A Python CLI designed to eliminate the friction of testing remote scripts. Instead of cloning repos, it bypasses the disk, fetches raw byte strings from GitHub, and executes them instantly inside a local subprocess sandbox. For people (me) too impatient to git clone.
Python 3 Core
GitHub Raw API
Subprocess Pipelining
Read Engineering Journal →
A remote code execution service built around ephemeral containerization. Untrusted C/C++ payloads are routed into restricted, zero-network Linux containers, compiled, and instantly destroyed to prevent RCE vulnerabilities. Kept alive by hope and a Render free tier.
REST API Gateway
Linux Containerization
GCC / G++ Toolchain
Read Engineering Journal →
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.
Bypassing localStorage limits using IndexedDB to build a browser-native coding environment, plus a tri-fold sharing mechanism so snippets escape the browser without needing an account.
A headless companion-device architecture that intercepts and archives message payloads before revocation packets can wipe them.
Re-architecting a coding assistant from an unstable web-scraper into an authenticated Python routing layer over the Gemini API.
Why XOR obfuscation falls apart under frequency analysis, and how a Scrypt-seeded keystream gets you real cryptographic entropy instead.
Using subprocess pipelining to pull remote GitHub scripts straight into memory and execute them without ever touching disk.
Mitigating RCE vulnerabilities with ephemeral, zero-network Linux containers and a WebSocket pipeline that streams output as it compiles.
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.
Educational Source-Available License (ESAL-1.0) — a strict anti-plagiarism license designed for academic submissions. My own software license, mostly to say "please don't copy this" in legal-sounding language.
A centralized file index and open-source repository for B.Sc. Computer Science coursework materials. Every practical I've ever suffered through, preserved for posterity.
Original Number Conversion Tool built to instantly convert between Binary, Decimal, Octal, and Hex bases. Because doing base conversion by hand is a war crime.
Legacy edition of the Number System Converter tool, preserved for networking and cryptography basics. Retired, but too sentimental to delete.
Published Python library. A utility package built for simplified statistical operations and mathematics, so I stop doing math by hand like a caveman.
The About Page Graveyard
The homepage isn't the only thing I've rebuilt seven times. The "About" page had its own quiet identity crisis, condensed here for your amusement:
- About v1 — The Material Design 3 Phase. Google Sans, a draggable floating profile bubble you could fling around the screen, anime.js entrance animations, and project titles that scrambled into emojis and binary. Deeply extra. My laptop fan still remembers it.
- About v2 — The Architect Era — serif headings, "Engineering Deep Dives," a full education timeline back to nursery school, live CPU load widgets nobody asked to see. Beautiful. Exhausting to maintain. You're looking at its plain-text retirement plan right now.
This is version 3. It will probably not be the last one either.
Congratulations, you now know more about me than my own extended family. Go drink some water.