Problems, and what they took

None of these arrived as a spec. Each one started as a symptom somebody was annoyed by. The interesting part is always the gap between the symptom and the cause.

ElasticsearchSearch relevanceDebuggingLLMSystem designCostBenchmarkingAutomationSelf-hostingRabbitMQMicroservicesNode.jsDeveloper toolingOpen sourceAPI designPlatformTechnical leadershipPerformanceInfrastructure

ElasticsearchSearch relevanceDebugging

Promoted listings that survive page two

LLMSystem designCost

Making LLM scoring repeatable enough to trust

BenchmarkingLLMCost

Choosing an LLM provider with numbers instead of vibes

AutomationLLMSelf-hosting

The weekly report that writes itself

RabbitMQMicroservicesNode.js

Service calls that survive a restart

Developer toolingNode.jsOpen source

The env drift that kept breaking deploys

API designPlatformTechnical leadership

An API platform partners could integrate without me

PerformanceCostInfrastructure

Finding the 40% of the cloud bill nobody was using

Let's talk

Let's talk

Let's talk

Let's talk

Got one of these?

If something in your system is slow, expensive, or nobody can agree why it's broken — that's the conversation I enjoy most.

[email protected]