Skip to content
Sid Prithvi

Work

Five things I've built. Two of them written up properly, from the problem to what shipped. Client work is described by what it is, never who it was for.

How I Work

  • 01

    Start at the problem

    Who has it, how often, and what it costs them. If nobody's written that down, nothing should get built yet.

  • 02

    Write it so it can be built

    Five years of PRDs and FRDs taught me the document isn't the point. The job is turning what the business wants into something a developer can pick up and build, and saying which parts are going to be expensive before anyone commits.

  • 03

    Decide in public

    A spec is a list of trade-offs, not a wish list. If I cut something, the reason goes next to it.

  • 04

    Build it to know it

    You learn more from a prototype than from any document, so I build one early and take it far enough that people can argue with it. I write the code when that's the faster way to find out.

  • 05

    Ship, then learn

    Real usage beats a roadmap. Put it in front of actual customers and watch one behaviour.