Here's a bit more about who I am, what I care about, and where I'm headed.
I'm a CS student at Rutgers who's into building things that solve actual problems. Not just theoretical stuff or assignments that get forgotten, but real apps that people actually use.
I got into CS because I liked the idea of creating whatever I could imagine. Want an app that tracks calories using AI? Build it. Need a platform for students to share course reviews? Make it happen. That freedom is what keeps me going, even when I'm debugging at 2am wondering why my code isn't working.
The best projects come from solving real problems. SmartEats exists because I was tired of guessing nutrition info. RUClasses exists because picking classes at Rutgers is confusing without insider knowledge. SleepView exists because I wanted to understand how ML works with health data. Each project taught me something new, not just about coding but about what makes a product actually useful.
I don't just want to write code - I want to understand the whole picture. How does this help users? What problem does it solve? Is this the best way to build it, or am I just doing it this way because it's familiar? Those questions matter to me and push me to keep learning.
Right now, my main goal is to land an internship or job where I can work on meaningful projects with people who know way more than I do. I learn best by doing and being around people who challenge me to think differently. I want to be in an environment where I'm constantly learning and getting better.
Long-term, I see myself working in full-stack development or maybe something with AI and real-world applications. I like building products that combine smart systems with great user experiences. The technical challenge of AI is cool, but what really excites me is making that tech accessible and useful for everyday people.
I also want to keep building my own projects on the side. Even if I'm working somewhere full-time, having personal projects lets you experiment with new ideas and tech. That's where some of the best learning happens - when you're working on something just because you want to, not because you have to.
Beyond career stuff, I want to get better at explaining technical concepts clearly. One of the most valuable skills in tech is being able to take something complicated and make it simple. Whether it's explaining your code to a teammate, writing docs, or presenting a project to non-technical people, communication matters. I'm working on that through this blog and by documenting my projects better.
I'd rather ship a simple, working product than spend forever perfecting something nobody will use. Done is better than perfect.
Tech changes fast. What worked last year might be outdated now. I try to stay curious and keep learning new things.
The best code in the world doesn't matter if nobody can use it. I care about making things that actually help people.
I like tackling challenges that require creative solutions. The harder the problem, the more satisfying it is to solve.
When I'm not coding, I'm usually still doing something tech-related - reading about new frameworks, watching conference talks, or brainstorming ideas for the next project. It's kind of a problem actually, but it's a problem I enjoy having.
I also spend way too much time on Reddit and Twitter keeping up with the tech world. New AI models, startup drama, debates about which JavaScript framework is best this week - I find all of it interesting, even if a lot of it is just noise.
Outside of tech, I'm into fitness and trying to maintain some kind of work-life balance (emphasis on trying). I've learned that taking breaks actually makes me more productive, even though it feels weird when you have a million things to do.
If you want to talk about projects, opportunities, or just chat about tech, feel free to reach out. I'm always down to meet new people and have interesting conversations.