Built by one person.
Fuelled by curiosity.

I'm NR. By day, I work in data and operations across Fortune 500 companies — the kind of environments where decisions are backed by numbers and every process gets stress-tested. By night, I build oddthree.

The name comes from a simple idea: three elements, one deliberately different. Look at the logo — three bars, two aligned, one tilted just enough to break the pattern. That's the design philosophy behind everything I ship: familiar enough to feel intuitive, different enough to be memorable.

My background in Industrial Statistics taught me to care about what the data actually says — not what sounds good in a pitch deck. That obsession with evidence shows up in the blog, where every claim links back to peer-reviewed research. And it shows up in the apps, where features earn their place through usefulness, not novelty.

I started with Breeze, a breathing trainer, because every wellness app I tried was either overloaded with features or buried behind a paywall. I wanted something that opened to a breathing exercise immediately, with zero friction. That's what I built.

Floravia came next — a period and cycle tracker that doesn't treat health data as a product to be sold. Everything is stored locally by default. No surveillance, no subscription required to see your own data.

Typefast exists because most typing trainers are either gamified to the point of distraction or painfully dull. I wanted something clean: open it, start typing, see your WPM, close it. That's the whole app.

TaskXP came from noticing that to-do lists don't account for the fact that humans are motivated by progress and reward, not just completion. TaskXP turns tasks into an RPG: earn XP for completing work, level up, maintain streaks. It's on Android.

PomodoroXP layers the same idea onto the Pomodoro Technique. Twenty-five minutes of focused work earns XP points, badges, and maintains a streak. The focus session itself is unchanged — it's still just a timer — but the surrounding system makes consistency more engaging.

When I'm not writing code or crunching numbers, I'm probably somewhere with a boarding pass. Travelling is how I recharge — new cities, new food, new perspectives. Some of the best product ideas hit me in airport lounges at 2 a.m.

This blog is where I write about the things I've learned — about breathing science, cycle health, productivity, and the process of building software as a solo developer. If you find it useful, I've done my job.

My degree was Industrial Statistics — design of experiments, statistical process control, regression modelling, and reliability analysis. Not the glamorous side of statistics, but the side that taught me to read a study with a sceptical eye: how was the sample drawn, what is the actual effect size, and would this hold up if you ran it again. Most of what I write up on this blog is filtered through that lens.

Breeze, the breathing app I built first, has logged over 5,200 user sessions to date. That dataset is small by industry standards but big enough to spot real patterns — for example, the fact that coherent breathing has the longest mean session length in the app shaped how I prioritise techniques in onboarding. When I cite Breeze data in a blog post, that is what I am talking about: aggregate session metrics from real users, not a marketing claim.

Every claim in a post links back to peer-reviewed research, with citations at the bottom. I do not run affiliate links or paid product reviews — there is nothing on this site I am paid to recommend. I write each post myself, using research I have read, and I revise posts when the underlying evidence shifts. The dateModified field on every article reflects that.