It started as a personal
tool.

Clinician by training,
builder by instinct.

I'm Nity - a urology SpR in the North West of England, and the person who writes and builds UroRef.

I trained in medicine at King's College London and took my MRCS with the Royal College of Physicians and Surgeons of Glasgow. Since then it has been the ordinary, unglamorous work of surgical training: clinics, lists, nights, on-calls, and the hundreds of small decisions that sit between them.

The other half of the story starts much earlier, and much further east. I grew up in Singapore, and my first websites were built in primary school with Microsoft FrontPage and basic Dreamweaver. That was as far as coding went for a long time. In between came the Singapore Youth Flying Club, two years of National Service in the army, and then medicine, which left little room for anything else. I only learned to code properly much later in life, teaching myself JavaScript and React in the gaps around hospital rota - and for a while the two lives ran quietly in parallel.

They collided on a urology on-call. The gap I kept hitting was never that the knowledge did not exist; it was that I could not reach it fast enough. So I built the thing I wanted in my pocket. That became UroRef, and UroRef became a family of tools - 3D anatomy you can turn over in your hands, a register that stops stents being forgotten, simulators that let you rehearse the operation before the operation.

These days I build in the open with the people who use it: trainees, trainers, and the BAUS Digital Innovation Group committee, where a lot of these conversations now happen.