Engineering notes

Arguments we have had internally, written down.

No case studies and no client names — the work sits under NDA. What is here instead is the reasoning: how we decide where a model runs, why rollback comes before features, and what we put in a contract.

How we work6 Oct 2026 · 6 min read

Fixed price or time and materials?

The argument is usually framed as trust. It is really a question about how much of the project is genuinely unknown.

Read the note

Applied AI28 Sept 2026 · 9 min

Grounding an assistant in your own documents

Most internal AI assistants fail for a dull reason: the model was fine, and the right paragraph was never put in front of it.

Read it

Product engineering19 Sept 2026 · 6 min

The seam where connected products fail

Hardware teams build good hardware. App teams build good apps. The product still fails, because the interesting bugs live in the gap neither of them was paid to own.

Read it

Applied AI2 Sept 2026 · 8 min

Edge or cloud: where should the model actually run?

“Edge AI” is sold as a category. It is really an answer to four specific questions, and if you ask them in order the decision usually makes itself.

Read it

Firmware & IoT18 Aug 2026 · 7 min

Ship the rollback before you ship the feature

The first over-the-air update is easy. It is the one that bricks four hundred devices in a warehouse you cannot drive to that decides whether your product survives.

Read it

Also published