Rithvik Senthilkumar

I turn unclear problems into systems that hold up.

I’ve been writing code for over a decade. What stuck is the habit. Understand the problem, design around real constraints, build the solution, then improve it from evidence.

GitHub LinkedIn

10+

years writing code

100+

builds, experiments, and prototypes

30+

tools, languages, frameworks, and systems

01 / Pattern

A long habit of making ideas real.

I’ve built countless projects over the years. Most were never published or polished into portfolio pieces. Small tools, bots, scripts, projects, rewrites, prototypes, and experiments taught me how to turn unclear problems into something concrete.

02 / Judgment

The work starts before the code.

I start by understanding the problem, then compare designs against constraints like scalability, complexity, maintainability, and user impact. The goal is to find an architecture that fits the problem instead of forcing the first idea that works.

03 / Execution

Useful systems beat theoretical designs.

I care about building systems that hold up in practice. That means modern architecture, testing, CI/CD, feedback loops, and the patience to iterate when the first version exposes what the problem really needs.

04 / Ownership

I take ownership of outcomes.

I do not think the work is finished because code exists. I take responsibility for the outcome: whether the system is clear, useful, maintainable, and improving after it reaches real people.