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:
Go 4 hrs 21 mins ⣿⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 27.62 %
TypeScript 3 hrs 29 mins ⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 22.12 %
C 3 hrs 2 mins ⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 19.28 %
Markdown 2 hrs 20 mins ⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 14.87 %
YAML 1 hr 5 mins ⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 06.91 %
🔥 Editors:
VS Code 10 hrs 21 mins ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀ 65.56 %
Cursor 5 hrs 26 mins ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 34.44 %
💻 Operating System:
Windows 9 hrs 10 mins ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 58.04 %
Linux 6 hrs 37 mins ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 41.96 %
I Mostly Code in TypeScript
TypeScript 28 repos ⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 53.85 %
Go 2 repos ⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 03.85 %
Shell 2 repos ⣿⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 03.85 %
Rust 1 repo ⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 01.92 %
Assembly 1 repo ⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀⣀ 01.92 %