yo, I’m Rehmatjot
*pronounced: reh-mat-jote
CS student by degree
systems engineer by questionable life choices
currently somewhere between:
"I should probably use an existing library"
and
"but what if I wrote the entire thing in Rust?"
what I do
I like understanding what happens underneath the abstraction.
Currently messing with:
- Rust
- distributed systems
- networking
- concurrency
- backend infrastructure
- OS internals
and enough DSA to occasionally question my life choices.
things I’ve built
[mini-redis] A Redis-ish TCP server in Rust because apparently HashMap wasn’t enough.
[MedVault-RS] Rust backend + PostgreSQL + Redis + authentication + an OCR/NLP service.
[more questionable projects →] you can see my repos ;D
stack
Rust · C++ · Go · Python · TypeScript · Java
Linux · Docker · PostgreSQL · Redis
my relationship with abstraction
high level abstraction
↓
"yeah but what's underneath?"
↓
read documentation
↓
read source code
↓
write a worse version myself
↓
understand it
currently learning
Rust
├── async
├── concurrency
├── networking
└── "why does the borrow checker hate me?"
systems
├── operating systems
├── distributed systems
└── low-level networking
stats, if you’re into that
LeetCode: 1914 Codeforces: 1105 Problems: 300+
⸻
Most of my repositories are just increasingly elaborate ways of answering “how does this actually work?”