LATEST ENTRY
Hibiscus: a Malaysian-built terminal for AI developers
Built in Malaysia for developers here, Hibiscus gives Pi a focused terminal workspace—with more care for the moments between prompts.
4 min readRead the entry
REKA BYTES / FIELD NOTESISSUE 001 · KUALA LUMPUR
Writing from inside the work
Journal.
What shipped, what broke, what it cost and the rule each mistake wrote into the codebase.
PRODUCTENGINEERINGDECISIONSCULTURE
7 published entries
THE ARCHIVE
Earlier entries
07 NOTES / UPDATED AS WE LEARN
- 014 min readRead article
We stopped designing our website like a product catalogue
We build products for clients, but our own site was making the products the main character. Here's why we changed the story, the navigation, and the invitation to start with a rough idea.
- 024 min readRead article
Green isn't proof — we make an AI watch the tape
Hiring a QA tester was never in the budget for a studio our size, so we built our own: tooling that films every UAT run and hands the tape to an AI that debugs what it sees — with screenshots as evidence.
- 0314 min readRead article
Seven days building Whimsery — the field report
One client game, seven days. The splash, the login wall, the button we deleted, combat juice on the network, and the eight bugs that almost shipped — everything the sprint taught us, in one place.
- 043 min readRead article
We shipped our own journal, then used it
Our studio has two surfaces: the academy, and the work we do for paying clients. This week both shipped off the same tool — a journal written in Markdown, stored in the repo, published by commit. Here's why one tool ended up serving both.
- 053 min readRead article
A free consultation is a weird business model. We do it anyway.
Most studios gate the first conversation behind a paid discovery call. We made ours free — the consult, the mockup, even the spec document is cheap enough to be a no-brainer. Here's the honest reason why.
- 062 min readRead article
Your app idea is not the hard part. The spec is.
AI can build almost anything now. Ask anyone who's tried — the failures almost never come from the code. They come from nobody having written down what "done" means.