↺ Back to hub

PandeAkshat / About — the story

About

Not a résumé. The story of how one instinct — repeat it, but a different way — survived thirty years, two degrees, and a few thousand nights of operational data. Five acts. Then two open doors.

Repetition, never the same way twice

As a child, I repeated things a lot — the same thing, done in a different manner each time. Riding the bicycle around the society, playing the same games, walking to the bus stop in the morning, every interaction at school: never about doing it better, always about trying out a different way.

That repetition laid the groundwork for a realisation I have never had to revise: there is more than one path to your goal. Efficiency is about finding the way that works for you — and automation is about making the path take fewer steps, for the same distance.

The four years that rearranged everything

At Amity, studying computer science, I met the first mechanism too large for any single mind — proper software. I learned quickly that I wasn't interested in writing code for its own sake. I was interested in what code makes possible when it is trusted with real operations: data that someone depends on, decisions that someone acts on.

That same restlessness brought me, in time, to the University of Bristol for an MSc in Financial Technology & Data Science — partly for the discipline of formal method, mostly for the honest question it asks of every model: what would you bet on this?

The working decade begins

I took the first professional post before the ink on the second degree had dried and have kept a dual rhythm since: consultancy that ships production systems, and platforms of my own that eat the same dog food.

At EXP-ER that meant building analytics infrastructures — ingestion, validation, reporting — for decisions real companies were making that week. At Dualchain, scale engineering: the unglamorous work of making a platform cheaper and faster without anyone noticing it happened. And alongside, the night audits at Sloane Square — a hotel ledger, reconciled by hand and then by Python, where I learned what 'numbers you can defend with your name on them' actually means.

What I keep learning

Every system I have built that people actually use has taught me the same three lessons, in the same order: automation is a moral act, validation is the work before the work, and no dashboard ever changed a mind — a meeting did.

The craft, as I practise it, is not analytics engineering. It is trusting machines with more of the operation so people can spend attention where machines cannot. Data is only ever the medium. The subject of every real project has been attention — where it is spent, what it is worth.

What is being built now

Today the work happens at Warehouse 47, a working venture studio — data systems, automation frameworks, and operational intelligence running inside live operations rather than beside them.

The long arc is simple to state and hard to do: a working demonstration that small, disciplined teams with good tools can operate at the quality of a large one. Everything on this site is downstream of that belief. Everything ahead of it is a test.

Working beliefs

  • Systems earn trust the way people do — a little at a time, under load.
  • The correct abstraction is usually the honest description, worded well.
  • Anything worth automating is worth logging.
  • Taste is compounding: every project should leave the next one sharper.

Two open doors

Both doors open on their own domains — Becoming is the public build-log, Curated is the personal list. Neither is a résumé; both are what the résumé is for.