Owning features end to end
I take features and tickets end to end, from the brief through to the review that lets them ship. The scope grows as capability does.
Hired the SD way: values first, craft always, AI fluency as standard. The tooling changes every few months; the standard the work is held to does not.
Contact me via:
What I am usually in the room for
The parts of the work I stay closest to.
- End to end, not handed off
- One person accountable from brief to merge. Work that changes hands three times is where the details go missing.
- Craft on the small tickets
- The unglamorous ones set the standard. A codebase is mostly made of small changes, so that is where quality is actually decided.
- AI fluency as standard
- Used where it helps, reviewed like anything else. Faster drafting does not lower the bar for what gets merged.
Get in touch
Questions for Vi, or for the team, ask away.
Got something
worth building?
Tell us what you're working on. You'll get an honest answer about whether we can help, and exactly how.
Start a conversation
Prefer email? hello@saigon.digital