What you are looking at
Every dot is one file of my own work, grouped by subject, oldest at the centre of each group. The bright ones are on this site. The mid-bright ones are earlier versions and direct ancestors of something shown. Everything else is the rest of the archive.
Engineering tools
Each is a single HTML file with its physics inside it. No server, no install. Several are checked against an operator's numbers or a MATLAB reference, and say so on the page.
From the archive
The browser tools are descendants. This is some of what they descend from: MATLAB written between 2015 and 2026, shown as it is, plus one older piece rebuilt as a live page.
Side projects
Built at home with the same single-file approach, mostly for my son and the youth baseball teams I coach. A fix found in one of these usually ends up in a work tool.
How these get built
Almost every tool here is based on code I developed over the previous decade, extended over the years by interns I directed. AI is very good at taking existing code and structure and producing a better version, and much less good at inventing a tool on its own. So the first move on any new problem is to find the closest thing that already works and build from it.
The archive behind this site is indexed so that step is quick: files, functions, version families and the code shared between them, with a written page for each recurring problem.
Rules the tools follow
- One file. Everything it needs is inside it.
- The engine touches no display code, so it can be tested alone and ported line for line.
- A port is checked against the numbers of the thing it was ported from.
- Where real operations data exists, the tool scores itself against it.
- Do the algebra on time windows, then measure. Sampling a grid first loses the short gaps that matter.