Currently banging my head against the kernel until it makes sense.
Send an Email • Website • LinkedIn • GitHub
I solve problems with code, mostly because I caused them in the first place.
By day, I build scalable applications (NestJS, NextJS, GCP, Etc). By night, I abandon high-level abstractions to break things closer to the metal. I don't believe in "magic" code. I believe in understanding the pointer arithmetic behind it.
Bridging the gap between "It works" and "I know why it works." I’ve centralized my documentation in the Engineering Journey monorepo, mapping the stack from logic gates to cloud infrastructure.
- Layer 1: The Hardware (Nand2Tetris): Demystifying the CPU. Built an assembler and VM translator to understand exactly how code becomes electricity.
- Layer 2: The Kernel (XV6 & Linux): The playground. Successfully recreated Go routines in C using RISC-V pipe syscalls and wrote my first Linux kernel module.
- Layer 3: The Application (C & Open Source): Mastering manual memory management and contributing to the real world (Merged PR for Nextcloud Server).
I don't claim skills. I show logs. Data auto-generated via WakaTime.
📊 This Week I Spent My Time On
💬 Programming Languages:
TypeScript 14 hrs 15 mins ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 56.39 %
Markdown 2 hrs 52 mins ⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 11.37 %
Go 2 hrs 4 mins ⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 08.22 %
Other 2 hrs 4 mins ⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 08.21 %
YAML 1 hr 17 mins ⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 05.09 %
🔥 Editors:
Cursor 22 hrs 45 mins ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣀⣀ 90.04 %
VS Code 2 hrs 30 mins ⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 09.96 %
💻 Operating System:
Windows 18 hrs 17 mins ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀ 72.36 %
Linux 6 hrs 59 mins ⣿⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 27.64 %
I Mostly Code in TypeScript
TypeScript 28 repos ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 52.83 %
Go 3 repos ⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 05.66 %
Shell 2 repos ⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 03.77 %
Rust 1 repo ⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 01.89 %
Assembly 1 repo ⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 01.89 %