Bibek Regmi
Full-Stack Engineer
I build products from the database to the interface.
- Node.js
- PostgreSQL
- Express
- React
- Next.js
- TypeScript
- Redis
- Docker
How I build software
Every product I ship is the same six layers. Pick one to see what I actually think about there.
API Layer
Every request is authenticated, then its payload is parsed through a schema before a single line of business logic runs. Invalid input never reaches the database.
What I think about here
- Authentication
- Authorization
- Schema validation
- Business logic
- Error shaping
Tools
- 01Verify sessionAPI
JWT signature + expiry
- 02Validate bodyAPI
Zod schema — reject early
- 03Check inventoryCACHE
Redis read-through
- 04BEGINDATA
Open transaction
- 05INSERT orderDATA
orders + order_items
- 06UPDATE stockDATA
Row-level lock
- 07COMMITDATA
All or nothing
- 08Invalidate cacheCACHE
Drop stale inventory key
- 09201 CreatedAPI
Location header set
Have a look around
A shell wired to the same database this page renders from. Try help, projects or stack.
bibek-regmi — interactive shell
Type "help" to see what this thing does.
Currently
- 01Building production systems end to end, from schema to interface
- 02Going deeper on PostgreSQL — query plans, indexing and transactions
- 03Getting comfortable with caching and queue-backed workloads in Redis
- 04Containerising everything I ship and tightening CI/CD
- 05Writing up what I learn instead of letting it evaporate
The longer version
Where I come from technically, and the handful of things I refuse to compromise on.
I am a full-stack developer who focuses on the Node.js (Express) backend and is comfortable with the core technologies around it — PostgreSQL, MySQL, MongoDB and Redis. I build server-side architectures that are fast to read and cheap to maintain.
On the front end I build highly interactive applications with React, Next.js and Vite, and I hold the same standard there: typed boundaries, predictable state, and no component doing three jobs at once.
I care about product experience and design detail as much as the code underneath. The goal is always a product that has both technical depth and obvious value to the person using it.
- Based in
- Kathmandu, Nepal
- bibekregmi4931@gmail.com
- Phone
- +9779866063568
Principles
- 01
Correctness at the lowest layer
Constraints, foreign keys and transactions belong in the database. Application code should not be the only thing standing between users and bad data.
- 02
Boring where it counts
Predictable, well-understood tools for the parts that must not fail. Save the novelty for problems that actually need it.
- 03
Ship it, then measure it
A deployed system that can be observed teaches you more in a week than a perfect design document does in a month.
Let’s build
something.
Got an interesting problem — a system to design, an API to untangle, a product to ship? I read everything that comes through here.
Kathmandu, Nepal · --:-- UTC +05:45