Ashish Narayan

Nirmalkaya, read as a problem that was diagnosed wrong first

Verify, do not reason

Where wellness begins.

  1. Cover
    01Cover — A ₹400 payment that produced nothing, and the three-word lesson the project took from it.Full size ↗
  2. The obvious diagnosis
    02The obvious diagnosis — Razorpay had no webhook configured. Clean, plausible, and it would have fixed nothing.Full size ↗
  3. What the machine had already said
    03What the machine had already said — One logged line, and a cause two files away from where anybody was looking.Full size ↗
  4. Twenty minutes, then the real work
    04Twenty minutes, then the real work — The fix was small. The redesign is the part worth showing.Full size ↗
  5. The same mistake, ten days later
    05The same mistake, ten days later — A number that was never in the system, written onto printed cards and four public pages.Full size ↗
  6. Four more of the same shape
    06Four more of the same shape — Every wrong turn in the record begins with confidence about a cause nobody had checked.Full size ↗
  7. Writing the guide is a debugging technique
    07Writing the guide is a debugging technique — Two of the last mistakes surfaced while writing instructions, not while writing code.Full size ↗
  8. Stated limits
    08Stated limits — What this study could not verify, and what it deliberately did not look at.Full size ↗

Executed by me — brand, product, systems and engineering — with an AI collaborator writing most of the code under constraints I set. Written from the project's own build log, decision log and version control. No metrics, testimonials or business results are claimed, because none are documented.

Back to the written studyAll case studiesSee it live ↗

B-SIDEOff the record
Verify, do not reason — the document — Ashish Narayan