Take it to the limit, then delete the rest.
Mathematician and data engineer. I run regulatory data at national-bank scale, and I write neural nets in C to make sure I still understand what’s underneath.
Pipelines, end to end
Ingestion to regulatory output, owned rather than handed off. FINREP, COREP, SIRBE, stress testing — filed, reconciled, defended.
Debugging by disaggregation
Split the thing until each part is small enough to be obviously right or obviously wrong. It has never failed to find the bug.
Removing the non-essential
I like systems pushed to their physical limits with the redundancy cut out — and AI used hard as part of how the work gets built.
Interview the page instead of reading it.
It answers from what I’ve actually built and shipped. If it doesn’t know, it’ll say so.
Pregunta en español o inglés — respondo en tu idioma · Ask in Spanish or English
Two AI teams cooperate through nothing but facial twitches — an órdago accepted on a tiebreak rule, a quarter of the channel lost to timing, and the harness catching an error I had already written into a draft.
Soft Actor-Critic implemented and pushed, plus an analysis of modern RL on continuous control.
What happens to a KAN when you swap B-splines for Taylor polynomials.
Many noisy annotators, one true label. A Bayesian way to decide who to believe.
Unfinished on purpose. If you have an answer, or a better question, I want to hear it.