Solve the problem before writing code
I spend time understanding the problem before thinking about implementation. A clear problem usually leads to a simpler solution.
About
I study computer science, write code, and design database tables. What I enjoy most is the step-by-step process of starting with a problem, drafting a layout, and making it functional.
Why I build
I enjoy the process of turning an idea into something real. There is a specific satisfaction in sketching a layout on a piece of paper, writing the code, and seeing it function. I don't build software to show off complex code; I build it because I like making daily life a little more orderly.
How I think
I prefer to understand the problem fully before opening a text editor. A confusing user flow cannot be fixed by writing cleaner code. I would rather spend two days figuring out the simplest layout on paper than write code I will have to delete later.
What I'm building now
Right now, I am building Rhythme—a daily planner that combines tasks, habits, and reflections on a single screen. I started it because I got tired of productivity apps that use constant notifications and streaks to capture attention. A planner should help you organize your day and get back to your life, not keep you staring at a screen.
Where I'm heading
I am a Computer Science graduate focused on becoming a disciplined product developer. My goal is to build software that lasts, which means choosing readability and solid fundamentals over temporary trends. I want to spend my career building simple, reliable tools that people use every day.
Building Philosophy
I spend time understanding the problem before thinking about implementation. A clear problem usually leads to a simpler solution.
Requirements evolve. I try to write code and organize projects so they can grow without becoming difficult to maintain.
Simple software rarely happens by accident. I prefer removing unnecessary complexity over adding more features.
Good software comes from balancing engineering, design, usability, and clear communication—not from technology alone.
The fastest way I learn is by creating real projects, making mistakes, and improving them over time.
Experience
2023
Independent Developer
Built web browser games to learn programming fundamentals and React state management. This taught me how even small changes in layout or latency change how a user feels.
2024
Technical Lead (Team Project)
A music recommendation web app built in a team of five. Instead of calling third-party recommendation APIs, we designed a custom scoring algorithm based on survey inputs and tag weightings. Shipped using Vite and React.
2025-Present
Founder & Developer
Building a personal focus product from scratch. Designing the interface, structuring the PostgreSQL schemas in Supabase, and building the Next.js frontend.
Skills