Skip to content
AIAn Alian Software company

Blog

Things we've shipped — and how.

Practical AI engineering. Architecture, guardrails, eval loops, and the production gotchas no one writes about. Filter by tag below.

Filter:

What we write about, and what we don't

Everything here comes out of engagement work rather than a content calendar, which shapes both the subjects and the tone.

Numbers with baselines attached
Where a post quotes a result, the before and after are both there. A percentage improvement with no starting point is unfalsifiable, and the AI industry currently runs on a great deal of it.
The parts that were harder than expected
Posts about builds include what went wrong — the retrieval that worked on curated documents and fell over on the real knowledge base, the eval case nobody thought to write. Those details are the reusable part; the happy path rarely is.
Written for the person who has to fund it
Most of these sit between a purely technical write-up and a business case, because that's where the decisions actually get made. Enough architecture to judge whether the approach is sound, enough cost and timeline to judge whether it's worth doing.
No model-release commentary
We don't publish reactions to every model launch. That writing ages badly and it's not what we know better than anyone else — what we know is what happens when these systems meet a real business process for six months.