The git log is the case study

People ask for case studies and I point them at the commit history. Every feature on this site started as a commit message. Stripe checkout, Google Calendar sync, client portal, admin dashboard, accessibility audit, newsletter, file uploads — each one has a SHA, a timestamp, and a description of exactly what changed. No after-the-fact narrative, no polished retelling. Just a sequence of decisions recorded in real time. The git log for jamesmusic.uk now has over thirty commits spanning three weeks. It reads like a product roadmap that someone actually executed. That is the case study. Not a PDF with before-and-after screenshots. A live repo you can clone, inspect, and verify. Every architectural decision, every bug fix, every integration — documented in the same place the code lives. When a potential client asks what my development process looks like, I do not open a slide deck. I open the changelog.