Engineering, backend APIs, full-stack apps, and applied AI.
The checklist we send every client after the deposit. Photos, specifications, copy, trust material and domain access — what to have ready so a build takes a week instead of a month.
Nine sections in the order a buyer asks for them, why specifications are the highest-value part of the page, and the two ordering mistakes that lose people before they reach the price.
Shop lighting, double compression and unpredictable crops — the four reasons good products photograph badly, and the fixes that cost nothing and work this afternoon.
An honest answer from people who build websites — including the four cases where a Facebook page really is enough, the four things it cannot do, and three questions that settle it.
A KHQR payment cannot be verified offline. Generating the QR locally, the pending-verification state machine, offline payment limits, and handling USD and riel in one drawer.
Most POS demos assume a working connection. Real shops do not have one. The architecture that keeps a till selling through an outage — and why offline-first is an ordering decision, not a feature.
The schema decision that makes offline sync work: store append-only stock movements and derive the level, so two tills syncing in either order reach the same answer.
Accepting a batch that contains sales you already have, per-sale transactions so one bad record cannot poison a batch, and what to do when two tills sold the same last item.
Writing a sale to IndexedDB, printing a receipt with no server, and an outbox that survives a browser crash mid-sale — plus why the stock number should say '~12'.
Honest market rates for web design in Phnom Penh — what $250, $900 and $3,000 actually buy, the running costs nobody quotes, and how to tell which tier you need.
