Things I build

The learning material has its own section: see learning sites. What follows is the other half of the work: small tools I write because a method is easier to use than to explain, and apps I build for myself.

Research tools

• Systematic review extraction and coding. Forms and pipelines that take a protocol and a stack of papers and produce a checked extraction, with the codebook applied consistently and every judgement traceable to the text it came from.
• Behavioural specification tools. Instruments that map an intervention description to the Theoretical Domains Framework, the Behaviour Change Technique Taxonomy and a fidelity assessment, so the specification is comparable across studies rather than bespoke.
• Grant and panel simulators. A set of reviewers that read a draft the way a funding committee would, with the scoring rubric applied explicitly and the weak claims named.
• Document-grounded assistants. Chat windows that answer only from a named source set. They are deliberately narrow: a small library, a visible refusal when the material does not support an answer. Several of the learning sites carry one.

Android apps

Small, finished things, written for practice rather than for a store. These are private builds at present.

• Academic Line Management. A game about the parts of academic work nobody trains you for.
• Keld. A cave flying game: take a craft into the rock, work the stations, bring the ore home.
• Cue and Whelm. Two smaller apps, still moving.

Code

Most of my public code sits on GitHub. The learning sites are static builds from plain markdown and a small renderer, which is why they load fast and survive being copied.

If you want to use any of this in your own work, ask. Most of it is shareable, and I would rather help than have someone rebuild it badly.