Localization,
deliberately done.
I write about what localization actually takes — the strategy, the workflows, and where AI genuinely helps. Ten-plus years localizing software alongside some of Silicon Valley's biggest names.
Currently in a full-time role, so I'm not taking on new client projects. The journal stays open.
Slower questions,
sharper systems.
Diagnose before you translate
Most localization problems aren't language problems — they're product, content, and process problems wearing a language costume. We start by mapping where strings actually come from, who owns them, and what 'done' means.
Workflows built for AI, run by humans
LLMs and agents change the unit economics of l10n. I design pipelines where machine output is reviewed, evaluated, and trusted — not just generated and hoped at.
Quality you can defend
A glossary, a style guide, and an LQA process that your engineers, PMs, and reviewers all use the same way. Boring, on purpose.
The journal is where the thinking lives.
Three essays so far: what makes software feel local, the difference between i18n and l10n, and where AI actually changes the pipeline.
Read the journal