I like building useful products, simplifying complex systems, and leaving behind notes that make future-me less confused.
🌊 Currently exploring reliable mobile systems, backend fundamentals, AI-assisted engineering workflows, and small tools that make development a little less painful.
- Software architecture beyond framework-specific thinking
- Systems that behave well even when network, devices, or releases get messy
- AI tools for code review, docs, automation and developer productivity
- Engineering notes, interview prep and public learning
- Building small useful things instead of only talking about building them
| Repo | What it is |
|---|---|
| ResumeForge | AI-assisted resume / cover letter tailoring experiment |
| android-knowledge-mesh | My Android learning and interview-prep knowledge base |
| DaggerHiltSample | A small DI sample while revisiting Hilt/Dagger |
| AndroidJobServices | Experiments around Android background work |
| WikiMobile | A simple Wikipedia search app |
Architecture that stays understandable.
Systems that work even when conditions are not ideal.
Developer tools that reduce repeated manual effort.
Code reviews that teach instead of just block.
AI tools that assist engineers without replacing judgement.Some repos are polished.
Some are playgrounds.
Some are just breadcrumbs from things I was curious about. 🧩
I don’t think good systems become reliable by chasing perfection from day one.
I like building something that works, observing where it bends, and improving it with care.
Reliability comes first. Elegance usually follows.
- 💼 LinkedIn — work, career updates and engineering thoughts
- 🧠 Stack Overflow — questions, answers and dev activity
- ✉️ Email — open to good engineering conversations