About

I’m an undergraduate computer science student who’s drawn to the parts of software that most people don’t think about: the error messages, the onboarding flow, the README that either makes sense or doesn’t.

Most of my work focuses on developer experience and documentation, making technical systems more accessible without sacrificing accuracy. I believe that clarity, by itself is a feature.

My approach is curiosity-driven. I learn by contributing, and I contribute by asking “why is this confusing?” or “how could this be clearer?” Sometimes that means rewriting documentation. Sometimes it means building tools to measure what “good” even looks like.

I’m especially interested in:

• Documentation tooling and best practices
• Developer experience as a technical discipline
• Open source community building
• Technical writing that respects both beginners and experts

Right now, I’m looking for opportunities to work with experienced maintainers, places where I can contribute meaningfully and learn from people who’ve been doing this longer than I have.

If you’re working on something where clarity and developer experience matter, I’d love to hear about it.