I build fast, test assumptions early, and reflect on outcomes not just code correctness.
Explore My Systems
I am driven by curiosity and a habit of learning through building. I think in systems breaking problems into constraints, feedback loops, and trade-offs and I prefer testing ideas in the real world rather than keeping them theoretical. I value clarity, simplicity, and understanding how things behave under real conditions.
Over time, I've learned to reflect not just on what works, but why it works. Building projects has trained me to identify gaps in my understanding, iterate quickly, and accept constraints as design inputs rather than obstacles. I care more about learning velocity and execution quality than surface-level outcomes.
Began learning programming through guided courses.
Explored game development and early logic-based projects.
Experienced limitations of hardware while building.
Learned: Persistence matters more than tools.
Experimented with multiple platforms and engines.
Transitioned from tutorials to self-driven experimentation.
Started understanding performance, constraints, and debugging.
Learned: Understanding systems is more important than finishing projects.
Entered a highly academic environment.
Reduced hands-on coding significantly.
Began observing problems through a business and systems lens.
Stepping away from tools can sharpen how you think about problems.
Did not actively build software projects.
Spent time thinking deeply about direction, interests, and long-term goals.
Developed a stronger interest in how businesses, products, and systems work.
Learned: Direction matters more than speed.
Faced significant personal and emotional challenges.
Productivity dropped, but self-awareness increased.
Questioned existing goals and reassessed what truly mattered.
Learned: Ignoring internal signals leads to burnout; alignment precedes execution.
Returned to building with clarity and urgency.
Designed and shipped multiple real-world systems independently.
Focused on speed, ownership, and learning through shipping.
Learned: Momentum comes from execution, not overthinking.
Exploration of structured service discovery systems.
Study of information aggregation for students.
System to validate physical-to-digital data mapping.
Experiment in logic, rules, and feedback loops.
Guess the right number
Your money manager
Exam Paper Creator
My personal dashboard
A short business quiz
Sales Data Entry
A Calculator
Save your name
Get time in dual format
Rock Paper Scissors against Computer
Start with a real constraint or friction point, not a solution looking for a problem.
Ship a minimal version quickly to test assumptions in the real world.
Watch how it behaves under real conditions and refine based on feedback.
Capture learnings about what worked, what didn't, and why.
Building a system to track and optimize daily routines based on energy levels and productivity patterns.
Exploring marketplace dynamics for hyperlocal service discovery with trust mechanisms.
Testing AI-powered tools for personalized learning path generation and knowledge retention.
Complete system for managing small local businesses - inventory, customers, payments in one place.
Verifiable skill assessments through real project challenges instead of resumes.
Community-driven news and updates system focused on neighborhood-level information.
Adaptive learning system that adjusts to user's context, energy, and understanding in real-time.
Built a complex feature-rich platform before confirming anyone wanted it. Learned to ship MVPs first and add complexity only after validation.
Stuck to my vision despite clear signals that users needed something different. Learned that ego can blind you to better solutions.
Spent months perfecting code without showing anyone. Learned that early feedback saves time and reveals blind spots.
Built projects based on hot technologies rather than real needs. Learned to start with problems, not solutions.