The primitive tools I am forced to use to build things you couldn't even conceptualize.

• Languages of Choice: C, Python, JavaScript
• Frontend Peasantry: Next.js
• Backend Sorcery: Node.js, FastAPI
• Data & Domination: PostgreSQL, Redis

I am currently babysitting a code execution platform because, apparently, you mortals cannot be trusted to run your own code properly. 👉 OopsEngine - Try not to break it.

Custom Unix Operating System Shell | C, Linux Kernel API, POSIX Systems

Yes, I built a custom Unix shell in bare-metal C. Why? Because the existing ones bored me to tears, and I prefer speaking to the Linux kernel directly. Middlemen are for peasants.

• Kernel Whispering: Architected a fully functional Unix shell, directly interfacing with the Linux kernel via system calls (fork, execvp, waitpid) to dictate process lifecycles.
• Flawless Orchestration: Engineered a dynamic multi-pipe parser for complex command chains (e.g., ls | grep | wc). I dynamically allocate File Descriptors and orchestrate IPC without deadlocks. Obviously.
• Stream Hijacking: Implemented standard stream hijacking using dup2() and open(). Because I route process outputs exactly where I want them to go.
• Custom Tokenization: Designed a custom two-phase string tokenization engine, completely circumventing the pathetic internal state collisions of C’s standard library.
• Memory Mastery: Enforced strict dynamic heap memory management. Zero memory leaks. Zero segmentation faults. Try not to weep at the sheer elegance of my REPL environment.

• LeetCode: Conquered 180+ problems (including the NeetCode 150) in Python. A mere cognitive stretching exercise before my morning juice box.

If you absolutely must interrupt my work, you may attempt to reach me here. I make no promises regarding a response.

• 🌐 Portfolio
• 💼 LinkedIn
• 🐦 Twitter/X

"Victory is mine!"