I build production LLM systems — observable, versioned, costed, deletable.
I multiplied the training data by 7.4× and the F1 score moved four hundredths of a point. A controlled NLP benchmark on what actually limits a problem — and the cheapest model that fits beating the impressive one that doesn't earn its cost.
Jun '26 A jailbreak is a regression, not a surpriseMost AI safety in production is one untested sentence in a system prompt. What changed when I started treating every attack that worked — fictional-framing, instruction-override, injection — as a regression test that runs forever. 442 cases, zero through.
Jun '26 Why "deletable" is the most important word in LLM systemsYou can delete the document. Its embeddings, cached answers, and summaries stay behind. The four layers of deletability, the architecture call that makes "delete everything" one line, and the cache that outlived a tenant I thought I'd erased.
May '26 Prompts deserve migrations, not vibesSchema migrations have versioning, rollback, and a paper trail. Most prompts in production don't. What changed for me when I started treating them the same way, and where it broke first.
Infrastructure traces tell you the request landed. Quality metrics tell you the answer was wrong. Until both share an ID, you're guessing. A pattern set from running this on call, and the one thing I'd build first if I had to start over.
"Tool calling with extra steps" is the wrong framing. The shift is smaller and weirder: the editor reads our Jira, our repo, our traces, and starts answering the questions I used to walk over to a teammate for.
Small tools I build for my own life. Each one started because something annoyed me enough to write code about it.
I'm a Senior AI Platform Engineer in El Salvador. I work from the same desk where I started in cloud infrastructure eight years ago. The systems have grown, the teams behind them too — but the principles haven't. Only the layer I apply them to.
I care about systems you can operate, not just demo. About prompts that fail loudly. About observability that survives the third on-call rotation. About cost lines that don't blow up the first time a feature gets traction.
Outside of paid work, I build small tools for my own life — usually with the same disciplines, because I don't know how to build software any other way.