Long pieces, short pieces, and an honest archive.
Featured essays are at the top. Below that, the steady stream of technical notes and project field notes — filterable by category. Most pieces are produced by our Article Crew and edited by a senior engineer. We publish what was hard, what was wrong, and what we changed.
The pieces we'd send a buyer first.
Long-form essays. The ones we'd put in front of a procurement reader, an engineer evaluating us, or a peer asking what we actually think.
Vibe coding is the on-ramp. Agentic engineering is the runway.
Karpathy named the move from typing code to specifying intent. After twelve months in production with it, here's what stays, what breaks, and what the actual discipline looks like.
Inside the Article Crew: nine stages, ten specialists, and a 95% claim-coverage gate.
The editorial pipeline we run inside WaterDoctor's backend. How one agent per stage, a verbatim-quote check, a Crossref DOI cross-check, and a live-URL fetch keep fabricated citations out of the prose.
Inside the WaterDoctor Crew: a research desk and a sensor-to-PDF agent on a weekly cadence.
Two pipelines, one weekly cadence, one human gate. How the WaterDoctor crew reads ten aquaculture journals, fact-checks every paper, then turns each pond's pH/DO/ammonia stream into a bilingual PDF the farm manager, the vet and the regulator can all read off.
If it doesn't have an eval harness, it's still a demo.
Five rules we use on every agentic build, drawn from a year of live client work, and the eval template we ship to every new engagement on day one.
IMDA's Model Governance Framework for Agentic AI, read by builders.
Singapore published the world's first agentic-AI governance framework in January. Here's a builder's-eye reading: which controls are zero-cost if you architect for them, and which ones cost real engineering hours.
Shorter, more often.
Technical write-ups, agent-team updates, and project field notes.
SQL Server hardening checklist.
Our working SQL Server hardening checklist — the controls that aged well kept, the ones that aged badly cut, and the ones that need new framing in light of MGF and modern Azure SQL.
Inside the Selection Crew: six analysts brief the buy, the buyer signs the PO.
How the Selection Crew briefs an e-commerce buy across six lanes — market intelligence, trend forecast, competitor radar, keyword research, arbitrage scout, sentiment — in EN ⇌ 中文, async, with a downloadable .docx the buyer signs before procurement moves.
AWS Network Firewall in front of an app server: the setup we'd actually use.
Default posture for putting AWS Network Firewall at the VPC edge in front of a public-facing app server, plus the agent-era addition.
Cloud security architecture for a medical group.
A dual-cloud (AWS + Azure) security architecture for a Singapore medical group: VPN, segmentation, ELK / OpenSearch, and the controls now in scope under MGF and PDPC enforcement.
Hospital visitor logging under PDPA: hashing, partial IC, and what we'd do differently.
Designing visitor logging for a Singapore hospital under PDPA — SHA-256-hashed IC numbers plus last-4-digit verification — and what we'd build today, given Singpass, MGF, and PDPC's evolved enforcement.
Inside the Image Crew: eight e-commerce roles, one anchor, brand-locked across six channels.
How we wired the Image Crew on the ArightAI platform — five analyst agents brief the shoot, a render agent ships the frame, a grader catches drift, an art director signs off. The anchor-first pattern that keeps two thousand SKUs in lock with one brand reference set.
Scaling a patient-management system without buying a bigger server.
How we got a 500K-client patient system on AWS back into reasonable response times without upgrading the host — splitting tiers, distributing cold data, and the agent-loop reporting pipeline that replaced template code.
Inside the BD Crew: six narrow scouts, a verifier, and a human in the only seat that signs.
How we built the bilingual EN/中文 BD pipeline that ships into WaterDoctor's CRM every week — six lane-specialist scouts, a deduping editor, a corroborating verifier, and a registry that grows by proposal, not by crawl.
Virtualizing a Windows Server 2000 box: the boring rescue, twenty years on.
Lifting a semiconductor-testing app off a dying HP ProLiant onto VMware vSphere — a reminder that the boring rescue still happens, and what we'd do differently if we got the same call today.
Automating Let's Encrypt for IIS: most of the C# is no longer needed.
When a custom C# Windows Service for Let's Encrypt automation on IIS still earns its keep — and when a maintained tool is the right answer.
Inside the Finance Crew: drafting the close, signing the file.
Five narrow finance specialists running the close cycle, financial statements and statutory filings for a Singapore SME caseload — every figure tied to a source row, every filing signed by a registered chartered accountant. How we wired the agent crew under the licence.
Watching RDP for brute-force: when the homemade service still wins.
Most teams should turn RDP off entirely. For the ones that can't, a small Windows Service watching Event ID 4625 still has its place — here's the design and where it fits.
When Excel VBA is still the right answer.
Why an Excel VBA build for a sales-order management system was the right call when the client's IT compliance gate was 12 months — and why the pattern shows up more often in the AI era, not less.
Cross-cloud business continuity for an ERP, and what we'd skip.
A BCM design for a Singapore real-estate agency's ERP — primary on AWS, secondary on Azure, JSON sync APIs, Windows resync service. What we'd cut, what we'd keep, and the SG listing-readiness angle.
EC sales systems for property developers.
Building an Executive Condominium sales-day system for a Singapore property developer: SFTP to HDB, SHA-256 columns, real-time OTP generation, and the launch-day playbook.
Pinning financial forecasts on Ethereum: what we tried, and what we'd do now.
We used Ethereum mainnet to pin SHA-256 hashes of quarterly forecasting parameters as a tamper-evidence layer. The use case held; the chain choice didn't.
Decentralized voting on Ethereum: what we tried, archived honestly.
We built a decentralized voting system on Ethereum + .NET C#. It was a working proof-of-concept. It was not a good idea. Here is the honest framing we should have led with.
Vitasg.SG: what the platform looks like in the agent era.
We build and run the eCommerce platform for Vitasg.SG: Shopee/Lazada/TikTok storefronts, a dedicated brand portal, our TECOM order processing layer, and the catalogue + customer-service agent crew that runs on top.
Condo management: the system we built, and the agent we'd add today.
Notes from running our Condo Management System in production: defect reports, voting, booking conflicts, and the one agent we'd add to the workflow today.
Smart Quotation, in the agent era.
Notes on plugging an agent into our Smart Quotation workflow: what changed, what we measured, and where the verification step matters.
Our 3G/4G SMS gateway is still running. Here is what we'd change.
Our industrial-grade SMS gateway is still in production at SG enterprise clients. The hardware estate has aged. The cellular generation has not. Here's the honest update.