Khaing Myel Khant is a lead product engineer and Myat Min Thu is a fullstack developer. Between us: qqPOS, PoPoTalk, and qqdraw — three products in production, used every day in Burmese and English. We work in AI, build with coding agents, and write down what we learn doing both.
Our stack
01
Yantaz is where we keep our work. Two people who design, write, deploy, and support the software we put our names on. Three products run in production today: a till for shops in Burmese and English, a conversation trainer, and a shared canvas with live cursors. When we learn something worth keeping, it goes into the writing. No pitch, no deck — just what we made and what it taught us.
02
Ours end to end — designed, built, hosted, and supported by the two of us.
Run your whole shop from one place.
qqpos.yantaz.com
Master the art of conversation.
popotalk.us
Pin it once. Everyone sees it.
qqdraw.yantaz.comAlso built with other teams
Read the entries03
How we build: the whole path from the first sketch to production scale, without handing the work around.
01
The problem worth solving, and the smallest version worth building.
We start with the people who will use it, not the stack. A few days of interviews and sketching is enough to tell a good idea from a crowded one — and to see what the first version should leave out.
02
Screens people can use without being taught.
Interaction design, visual systems, and the hundred small decisions that make a product feel finished. Designed and built by the same people, so nothing is lost in a handoff.
03
Typed, tested, in production early.
Web and mobile applications with typed APIs, real data models, integrations, and AI features where they measurably help. Production from the first week, not the last.
04
Shipping is a button, not an event.
Reproducible infrastructure, CI/CD, environments, and monitoring — so a release is routine and a failure is visible before a customer reports it.
05
The next ten times does not need a rewrite.
We stay after launch: performance, cost, database load, and the operational work that keeps a product online as usage grows.
Production in the first week, a working slice every Friday, and timelines measured in weeks, not quarters.
Typed end to end, tested where a failure would be expensive, and deployed behind staged rollouts you can undo.
Accessibility, performance budgets, and a design system that survives the next feature — not a deadline casualty.
04
Three things we have done long enough to call expertise, each one carrying a product in production.
01
AI carrying part of the product, not a chat box bolted onto it.
PoPoTalk scores a live conversation on tone, engagement, empathy, and timing — streaming output, structured responses that survive a bad generation, scenario retrieval, and evaluation before a model change reaches users. Model quality is treated like any other measured behaviour.
02
We build with coding agents the way we use compilers: constantly, and with review.
A written scope becomes the agent's brief, repository conventions tell it where things belong, and the type checker and test suite decide whether a change is allowed to land. Both of us read every diff. That is where a first deploy in a week comes from — the agents do the typing, we do the deciding.
03
The first sketch and the third year of support, from the same two people.
Interface, data model, payments, deploys, and the inbox afterwards. All three products here were built this way and are still run by the people who built them, which is the only evidence of end-to-end ownership we think is worth much.
05
When we take a build on: a reply in a day, a written scope before code, a demo every Friday, and a handover that runs without us.
01
One business day
You send the problem, the deadline, and the constraint you cannot move. We reply with what we would do about it, or say plainly that it is not our work.
02
3–5 days
Screens, the data model, and the risks we can already see, in one short document. You approve it before anything is built.
03
Every Friday
Production deploys from the first week and a walkthrough every Friday. You watch the software change, not a status report.
04
Ongoing
The repository, the documentation, and the credentials are yours. We keep running what we host, or hand it to your team.
Our best referenceis softwarewe run.
qqPOS keeps shops, cafés, and restaurants selling in Burmese and English, online or off. PoPoTalk scores every message of a practice conversation on tone, engagement, empathy, and timing. qqdraw drops a team’s references and cursors onto one board with no save button. All three are live, ours, and supported by the two of us.
Questions about a product, a note on something we wrote, or an idea you want a second opinion on. One of us reads it and replies within one business day.
