Skip to content
NBN TECH
Get in touch
About

An engineer, not a template.

NBN TECH is the practice of a software engineer who has spent years shipping real products — not demos. I work across the whole stack: the interface a customer touches, the API behind it, the database it leans on, and the cloud pipeline that deploys it on a Friday without anyone holding their breath.

I care about the unglamorous parts — observability, migrations, error budgets, the second release — because that is where projects quietly succeed or quietly rot. If you want someone who treats your codebase like it has to outlive the engagement, we'll get along.

NT
How I work

An approach to engineering.

Principles that show up in every engagement — the difference between code that ships and code that lasts.

01

Own the outcome

I don't hand over a codebase and disappear. Success is your product working in production, not a green checkmark on my machine.

02

Boring on purpose

Proven tools, tested migrations, monitored releases. The interesting parts of engineering should be your product, not my infrastructure.

03

Write it down

Decisions, trade-offs and runbooks live in the repo. Your team should be able to own what I build without a phone call to me.

04

Ship in the open

You watch the work land in a live environment continuously — no month-long silence ending in a big reveal.

The engagement

How projects run.

A predictable path from first conversation to a product your team can own.

01

Discover

We pin down the real problem, the constraints, and what success actually looks like — before a line of code is written.

02

Design & Plan

Architecture, data model, and a milestone plan you can see. No black boxes, no surprise scope.

03

Build

Shipping in small, reviewable increments. You watch it come together in a live environment, not a status meeting.

04

Launch

A careful release: migrations rehearsed, monitoring in place, rollback ready. Launch day is boring on purpose.

05

Support

The second release matters as much as the first. Ongoing fixes, iteration, and a codebase your team can own.

Let's build something that lasts.

Tell me what you're trying to ship and where it's stuck. I read every message myself and reply within two business days.