Residues

Things fade.

Not immediately, but over time. The struggles, the breakthroughs, the hard-won lessons, they don't all stick. At least not for me. Unless I write them down somewhere, they tend to slip away.

This blog started as a way to keep track of those learnings. Not as complete guides or final answers, but as reminders of what actually helped when I was in the middle of figuring something out.

Over time, I realized that what I was writing wasn't the full story of the work, it was the part that remained after the confusion, experiments, and false starts had settled.

Those leftovers are what I call Residues.

This space is a collection of them.

I'm Praveen, a data scientist.

I spend most of my time working with data and systems, building models, writing code, and trying to make sense of messy problems. A lot of what I do sits somewhere between analysis and engineering, and I'm constantly learning as I go.

I'm not writing this as someone who has everything figured out. Most of what you'll find here comes from being in the middle of the work: trying approaches, getting things wrong, revisiting assumptions, and slowly forming opinions that may change over time.

If you notice gaps, mistakes, or things that could be better explained, I genuinely appreciate hearing about them. This is a learning log first, and it's better when it's corrected or challenged thoughtfully.