United Kingdom / Software & product
I build software for private investors — tools that handle the parts of the job that are tedious, error-prone and unforgiving of mistakes. Previously eight years in banking.
I spent roughly eight years in banking before moving to independent software and product work. The overlap turned out to be larger than I expected: both are about getting numbers right, keeping a record of why they are what they are, and being able to prove it later.
Everything I build now sits at that intersection — financial data, tax and reporting rules, and interfaces that make a complicated position legible at a glance. I work mainly in Python, and I care more about correctness and auditability than about shipping quickly.
Earlier work included a period at Keltech.
Python · PySide6 · SQLite
A desktop application for running an options wheel strategy end to end — cash-secured puts, covered calls, assignment and rolling — with UK tax reporting built in rather than bolted on.
The difficult part of the wheel isn't the trading, it's the accounting. Assignment changes your cost basis. A roll closes one position and opens another on the same day. Premiums, fees and currency conversions all have to land in the right place, in the right tax year. Do it in a spreadsheet and it starts falling apart within a few months.
So the application handles Section 104 pooling, foreign exchange at the correct rates, and a full audit trail behind every figure — then produces the CSV and PDF outputs a capital gains return actually needs. It also tracks performance across positions, so you can see whether the strategy is doing what you think it is.
Thirty-one releases so far, and still in active development. More at optionswheeltracker.com.
JavaScript · No backend · Nothing leaves the browser
A prayer times site. Everything is worked out on the visitor's own device from their coordinates, so no location data is sent anywhere, there are no accounts and no tracking, and the whole page is a few tens of kilobytes.
It looked like a small project and turned out not to be. The astronomy is settled, but very little above it is. Different bodies place dawn and nightfall at different angles below the horizon. The schools of law differ on Asr by up to an hour. And above roughly 48° of latitude there are weeks each summer when the sky never gets properly dark, so the two twilight prayers have no observable moment at all — London loses true darkness for about two months of the year, Glasgow for closer to four.
So the site shows its working. It names the method it is using, marks times as estimated when they have been derived rather than observed, explains every setting in plain language, and carries the London Unified Prayer Timetable — the published table most mosques inside the M25 follow, which no calculation reproduces — as published rather than approximated.
There is also a diagram of the sun's full daily path with the horizon drawn through it, because the two prayers people find hardest to picture are the two that happen while the sun is below that line.
Free, no adverts, at ummahsalah.com.
Why the wheel is simple to run and genuinely awkward to account for — pooled cost basis, the thirty-day matching rule, assignment, and the currency problem sitting underneath it all.
Notes from building Ummah Salah — which angle counts as dawn, what happens to Fajr and Isha in a northern summer when the sky never fully darkens, and why the timetable most London mosques follow cannot be reproduced by any calculation.