Working with me.

A short manual for teammates and hiring managers: when I am around, how I talk, how code ships and what happens when something breaks.

Hours and time zone

I work from Kathmandu, Nepal (UTC+5:45). My core hours are 10 AM to 8 PM Nepal time. That overlaps well with Europe, the Gulf and Asia.

How I communicate

  • Written first. Plans, decisions and handovers go in writing, so nobody needs a meeting to catch up.
  • Short, regular updates. What shipped, what is next, what is blocked.
  • Bad news early. If something will slip or something broke, you hear it from me first, with what I am doing about it.
  • Questions early. I would rather ask a quick question on day one than guess for a week.

How code ships

  • Every change goes from tests to staging to production. Nothing goes straight to live.
  • Changes are small and easy to roll back. Risky moves sit behind switches, like the per-route switches I used to move Laayo from Laravel to Go.
  • Each feature gets a security review before it ships.
  • After a release I watch errors and speed, not just the deploy log.

Code review

I like small pull requests with a clear reason in the description. When I review, I look at correctness and failure cases first, then readability, then style. I explain the why behind a comment, and I am happy to be told I am wrong.

When something breaks

  1. Stop the damage first: roll back or switch the feature off.
  2. Tell the people affected, in plain words.
  3. Fix the cause, then write down what happened and what changed so it does not happen again.

Leading a team

I plan the week, split work into clear tasks with one owner each and keep everyone on one shared plan. My job as a lead is to unblock people fast and keep the bar high without slowing the team down.

In short.

Team management

I lead the team behind Laayo: riders, store partners and the people who keep orders moving. I plan the week, split the work into clear tasks with one owner each, and keep everyone on one shared plan so nobody is stuck waiting. As Event Manager at JCI Nepal I run events with volunteer teams from plan to wrap-up.

Production-level code quality

Every change goes from tests to staging to production, never straight to live. I write typed Go and TypeScript, keep code small and readable, review security on each feature, and watch errors and performance after every release.

Reliability and communication

Laayo takes real orders and real payments every day, so I build for failure: health checks, alerts, backups and fast rollbacks. When something breaks I say so early, explain it in plain words and follow up with what changed.