About
Few projects at a time, each one owned by a person
One person building software in Vietnam. I take on few projects at a time, because that is the only way each one has a person who genuinely holds it and can answer any question about it.
How the work runs
- Projects at a time
- Three at most
- Delivery rhythm
- Every two weeks
- Accountability
- One named person per project
- Working languages
- Vietnamese and English
- Code ownership
- Yours, from day one
- 10
- projects published
- 9
- technologies in real use
- 8+
- engineers on my deepest stack
- 1
- business day to reply
Commitments
Four things I commit to
Written so you can check them. If I fail one of these, you can point at it rather than argue about impressions.
- 01
The code is yours from day one
The repository is in your name, not mine. So are the domains and cloud accounts. You can walk away from me at any point without losing anything.
- 02
Scope written down before work starts
The scope document is part of the contract, including an explicit list of what falls outside it. Changes are priced before they happen.
- 03
Bad news travels fast
If something is running late, you hear about it that week, not at acceptance. I raise the problem with two or three ways forward and what each costs.
- 04
I say no when I should
If an off-the-shelf platform suits your problem better than custom software, I will say so. A project that starts wrong helps nobody.
My own product
I run a real product of my own
A free bilingual AI music library. It is not a side project for show: it uses the same stack, the same process and the same standards I apply to client work, including the legal and admin sides. If you want to see how I work before signing anything, open it and look.
Open the music library