Search

Search work, writing, and fragments.

edition / 01/26

selected work / notes / experiments

Software engineer / systems, tooling, and verification

I build software that is clear to use and solid underneath.

I work on software where the surface and the internals both matter: study tools, privacy-heavy systems, verification paths, and machine learning with a clear job to do.

  • currently Computer engineering student / Kathmandu University
  • care about Software that earns trust quickly and still makes sense once you look underneath.
  • on github shuv-amp ↗

selected work

2026

Protocol tooling / verification

SP-DIFFER

A correctness harness for BIP 352 Silent Payments implementations, with differential adapters, replayable regressions, and release-verification lanes.

Maintainer-acknowledged upstream bug reports across multiple implementations, with one reduced case later folded into merged BIP-352 test-vector coverage.

2026

Applied ML / decision support

Fluvius Predict

An uncertainty-aware hydropower decision system that turns ground-sensed river data, weather and melt signals, and plant availability into discharge forecasts and safer energy commitments.

Overall winner and Hydropower & Sustainable Energy Track winner at JunctionX Kathmandu 2026, earning Team Pikachu a Golden Ticket to the global Junction stage in Finland.

2025

Full-stack software engineering

TestLoom

An exam-prep platform that turns scattered study material into a more usable learning system with OCR, adaptive practice, and collaborative tools.

One codebase carrying OCR ingestion, question banks, analytics, auth, and deployment, so it holds up as a full product build rather than a single polished feature.

writing

Aug 15, 2026

9 min read

Nobody Brings Food When You Are Happy

On good news, the faces people make when they hear it, and why being celebrated is so much harder to receive than being pitied.

Jun 28, 2026

3 min read

The Biscuits Are Still Here

Riki lived next door, but our house kept food for him. After he was given away, his biscuits remained—and Tiger kept waiting.

what stays consistent

The domains can change. The standard does not: understand the problem fully, choose the shape with restraint, and make the engineering stand up in real use.

Note 01

Make the product easy to trust before trying to make it impressive.

Note 02

Let the architecture do the heavy lifting quietly.

Note 03

Keep choosing work that stretches judgment, not just output.