§ blog · Technical articles48 posts
Insights

Technical notes from our Pilot Builds.

Reference architectures, technology selection criteria, and rollout roadmaps — written for people who'll actually read the code and run the system, not company news.

Optimization LoopMeasurementOptimisationStatistics

Before running an A/B test, work out one number — for most Vietnamese sites it exceeds a year of traffic

You do not have to run an A/B test to find out whether it can conclude anything. One calculation, about a minute's work, gives the minimum number of visitors required. For a site with 500 visitors a day, detecting a 10% improvement needs 322 days — and the habit of checking results daily pushes the false-win rate from 4% to 20%.

13/09/202611 min read
AI & MLGPT-6CybersecurityAI cost

GPT-6 Astra: skip the AGI claim, these three numbers are the ones that matter

On 3 September OpenAI released GPT-6 Astra, and the company's president said it might come to be seen as AGI. For anyone who has to make a decision, that sentence is close to unusable. Three other numbers from the same day are not: a risk rating no model had reached before, a 37-point gap on the same test, and a price 2.5 times higher.

03/09/202611 min read
DevelopmentOpen SourceTypeScriptUI Components

Forge Dialog: dialogs built on the native <dialog> element, with no z-index left to hunt

An admin page needs to ask "are you sure you want to delete this?". The browser's built-in confirm can do it, but it freezes the whole page and cannot be styled; the usual replacements drag in a framework. Forge Dialog is how we solved that for our own products: no runtime dependencies, built on the native dialog element, with React, Vue and Svelte adapters inside the same package.

02/09/20269 min read
Data AnalyticsDashboardsData AnalyticsDigital transformation

The dashboard was delivered and nobody opens it: the tool is not the problem

A company pays for a reporting screen, the handover goes well, and three months later nobody opens it. The first instinct is to blame the software, or to blame staff for not being comfortable with numbers. One figure shows both explanations miss: inside the same company, executives use it around 80% while employees use it around 26% — same software, same data, same screen.

14/08/202611 min read