Most software begins with an idea.

Mine usually begins with frustration.

A confusing process.

An outdated workflow.

A problem everyone has accepted.

I enjoy finding those moments and asking:

"If we were building this today, would we build it this way?"

If the answer is no, I start designing.

Not because I enjoy writing code.

Because I enjoy removing unnecessary complexity.

That's the reason this GitHub exists.

Not to collect repositories.

To document problems that became products.

You'll notice a pattern if you explore my repositories.

I don't build around technologies.

I build around questions.

Questions like:

• Why is startup equity still difficult to understand?
• Why should market research overwhelm instead of guide?
• Can software encourage better conversations around social issues?
• Why are traditional businesses still forced to use outdated tools?

Those questions eventually became software.

A platform designed to help startup employees understand the true value of their equity through vesting simulations, ownership insights and financial clarity.

Problem: Equity is valuable only when people understand it.

An AI-assisted market intelligence platform focused on helping people understand markets instead of drowning them in data.

Problem: Better decisions come from better understanding—not more information.

A product exploring whether technology can encourage more thoughtful conversations around a deeply rooted social issue.

Problem: Some challenges deserve analysis, not assumptions.

An anonymous communication platform designed around simplicity, privacy and honest expression.

Problem: People often need a safe space more than another social network.

Software designed to modernize the day-to-day operations of traditional chit fund businesses.

Problem: Reliable businesses deserve modern tools too.

Every project follows the same path.

Observe

↓

Question

↓

Understand

↓

Design

↓

Build

↓

Refine

↓

Ship

I don't believe software becomes valuable because it's technically impressive.

It becomes valuable when people stop noticing the complexity it removed.

These are tools—not identity.

Python • Java • TypeScript • JavaScript • SQL • C++

Spring Boot • Flask • REST APIs • Node.js

React • Next.js • Tailwind CSS

PostgreSQL • MySQL • Supabase

Git • Docker • Vercel • Postman

• Product Engineering
• Backend Systems
• Artificial Intelligence
• Financial Technology
• Business Software
• Developer Tools
• Human-Centered Design

I'm working toward becoming someone who isn't remembered for knowing the newest framework.

I want to be remembered for recognizing meaningful problems early and building software that makes those problems simpler.

If my work becomes genuinely useful, the technologies behind it won't be the most interesting part.

The impact will be.