Blog
Field notes from 9 years of shipping backend systems, trimming cloud bills, and putting agents in front of real users. Specific over general.
What the AI engineering market actually wants in 2026
I read a lot of job postings and hiring reports this autumn to recalibrate my own stack. The signal is clear and a little humbling: agents, retrieval, evals and shipping to real infrastructure, with model hosting and fine-tuning further down than the hype suggests.
AG-UI: the missing protocol between your agent and your frontend
A2UI: when the agent builds the interface
Evals are the product: how I ship LLM features without guessing
The favour that became a revenue line
Fine-tune, retrieve, or just prompt? A decision I keep re-making
Shipping an AI copilot from a hackathon to production
From 3.5 hours to 20 minutes: rewriting a nightly SKU sync
How we cut infrastructure cost by ~60% with spot instances and Kubernetes
Dropping Selenium made our crawler 15× faster