/ Profile — About
I’m Alexanders. I build
products end to end.
Full-stack and AI engineer in Jakarta. For the F&B and beauty brands I work with, it usually starts before the code — the logo, the brand, the space itself — and ends in the software they actually run on: the booking site a beauty studio takes deposits through, the register a restaurant keeps selling from when the wifi drops, the AI that answers its customers on WhatsApp. I like the problems where the details decide whether it works.
/01—How I work
I start with the real constraint, not the framework. The customer who exists three times in the database. The cut the aggregator takes. The network that drops mid-sale. Design outward from those and the architecture mostly picks itself.
I build with AI, and I ship AI — but I hold it to the same bar as everything else. It works from real data, uses cheap models for the cheap work, fails open instead of locking people out, and stays switched off until it has earned its way into production.
I keep the seams tight. A marketing site and a live app have no business sharing a deploy, so they don’t. Each piece stays fast, and small enough to reason about at 2am.
Design tokens and types are the source of truth, tested together. Otherwise the system drifts quietly the week after launch, and nobody notices until a customer does.
/02—Principles
It has to survive real users
A booking page that takes actual deposits. A register that keeps working when the wifi dies. If it only holds up in a screenshot, I’m not done with it yet.
This site is the proof
You’re looking at the work right now. It runs the same stack I write about and ships almost no JavaScript unless a demo needs it. If it felt slow, that would tell you plenty.
I build with AI, and I ship AI
AI helps me move faster, and it’s in the things I ship — an agent that books over WhatsApp, vision that reads a job off a flyer photo, moderation that lets people through when it isn’t sure. I give the model a narrow job, watch what it does, and keep it switched off until it earns its place.
Range, without the mess
A marketing page and a Rust register don’t have much in common. I’d still like them to feel like they came from the same person — doing a lot of different things shouldn’t look like doing them at random.
/03—Stack
React · Astro · Next.js · TanStack Start · React Router · Vite · TypeScript · Tailwind CSS · React Native
Node · Next.js API · Astro Endpoints · Drizzle ORM · Zod · REST / Webhooks · Web Push
Turso (libSQL) · SQLite · Vercel · Upstash · Sentry · Xendit · Tauri · ESC-POS
TypeScript · Rust · C# · C++ · SQL · Anthropic API · Context7
/04—Timeline
- 2026Built the offline-first POS: a Tauri/Rust register that recovers from a crash without losing a sale, prints its own receipts, and runs on a design system tested in lockstep.
- 2025A busy year — the commerce backend, the WhatsApp customer-service agent, the booking system with one clean customer record, and the restaurant’s own delivery app.
- 2024Brand sites the owners actually run themselves, and a job board built around not getting scammed. Fast, editable, and Lighthouse ≥ 95.