About

The person behind the over-engineering.

I'm Mark — I work in finance, write Python, and spend more time than is strictly necessary thinking about tennis statistics. This blog started as a way to write up the things I was learning on the job and keep myself honest: if I can't explain it clearly, I probably don't understand it well enough yet.

My background isn't traditional computer science — I came to programming through finance and figured most of it out as I went. That shapes how I write: I try to assume as little prior knowledge as possible and build things up from first principles, because that's genuinely how I had to learn them.

What I write about

• Quantitative finance — delta hedging, log returns, risk-neutral pricing, fat tails
• Statistics — the kind of questions you should ask but rarely do (why n-1? why std over MAD?)
• Python — environments, random number generation, vectorisation, the module search path
• Tennis — match simulation, scoring theory, and a slightly unhealthy relationship with Tennis TV
• Anything else — a seven-part investigation into whether I should stop eating meat counts, apparently

The name

One Equals One is a nod to the kind of thinking I try to bring to everything here: start from what you actually know to be true, and build carefully from there. No shortcuts, no black boxes.

Get in touch

You can find me on Medium where these articles were originally published. Feel free to reach out if something here was useful — or if you spotted a mistake.