01
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 and build software products. What I enjoy most is the process of taking a problem, thinking through how it should work, and turning the idea into functional software.
Motivation
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.
Methodology
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.
Current Work
Right now, I am building Rhythmé—a Personal Alignment System that unifies execution (tasks, habits, deep work) with emotional awareness (zero-knowledge encrypted reflections) and explainable behavioral mathematics. I started it because I got tired of fragmented productivity apps that use constant notifications and punitive streaks to capture attention. A good system should act as a thoughtful mirror, helping you build momentum without overwhelm.
Vision
I am a Computer Science Diploma 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
Core beliefs that guide how I design databases, write clean functions, and make product decisions.
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
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.
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.
Founder & Full-Stack Architect
Architecting a Personal Alignment System from scratch with Next.js 16 and Supabase. Implementing client-side zero-knowledge AES-GCM-256 encryption, explainable statistical behavioral correlation models, and sub-50ms optimistic UI workflows.
Skills