Backend engineer. Distributed systems enjoyer. Professional bug hunter. Occasional bug creator. Relentless bug eliminator.
I build systems that move data fast, fail loudly, and recover gracefully.
Most days I am:
- Designing systems that handle load without drama
- Hunting latency like it owes me money
- Reading source code when the docs are lying
I like problems that involve scale, performance, reliability, and weird edge cases.
- Measure first. Optimize second.
- Logs are a conversation with your future self.
- KISS - Keep it simple, stupid. Complexity is the enemy of reliability.
- If it breaks in production, it was already broken.
- Distributed systems and consensus protocols
- High-throughput Java backend services that don't apologize for existing
- Caching strategies and performance optimization
- System design at the edge of what's comfortable
- Building things that survive traffic spikes without a postmortem
languages
backend — the interesting part
infra
frontend — handle with care. do not mention at 9am.
tools
"1200 problems in. still not impressed with myself. still going."
🥬 LettuceCache LLM kept re-running identical expensive queries like it had no memory. Which it didn't. Fixed it with Redis + semantic search. Redis is now confused but cooperative.
| 🚦 Quasar Taught a camera to detect and judge traffic. 90% accuracy. The 10% it misses? Motorcycles. Every time. Without fail. Motorcycles specifically.
|
🤖 Stree AI Chatbot Chatbot with actual context retention — a concept most chatbots treat as optional. Solved it. Shipped it. Moved on before I could overengineer it.
| 😏 Sarcasm Detector Fine-tuned a transformer on Reddit. The model now assumes everything is sarcastic and trusts no one. Accurate. Relatable.
|
