Projects · Experiments · Technical investigations
This is where I collect the things I build while investigating awkward technical problems, experimenting with new tools and looking for better ways to connect systems, people and information.
CURRENTLY ON THE BENCH
AI-assisted documentation workflow
Turning difficult bugs into clear explanations
Placeholder for whatever I become obsessed with next
Featured project
A working application that analyses merged product pull requests, checks the customer help documentation and prepares a documentation pull request when something needs to change.
AI agents · GitHub APIs · Human review
DocBot retrieves product changes, reads the relevant help content, explains whether an update is needed and creates a reviewable documentation pull request.
The project explores agent orchestration, repository state, overlapping product changes, structured output, feedback and the point at which human judgement should remain firmly in charge.
Designed and built from scratch
A lightweight, responsive static site built with plain HTML, a shared CSS design system and a tiny amount of JavaScript.
HTML · CSS · JavaScript · Responsive design
I designed and built this site to present my work clearly without hiding it inside a large framework or complicated build system. Each page is ordinary semantic HTML, the visual language lives in one shared stylesheet and JavaScript is used only where it adds something useful.
The navigation is the main shared JavaScript component. Everything else is handled by the browser using HTML and CSS: layout, spacing, typography, responsive behaviour, project cards and visual hierarchy.
I chose this approach because the site does not need application state, a database or client-side rendering. A static portfolio should load quickly, remain easy to understand and be simple to change without introducing unnecessary dependencies.
Why build it this way?
A portfolio is mostly structured content. It needs strong visual design, clear navigation and responsive layouts, but it does not need the machinery of a full web application.
Keeping the implementation small makes the site easier to debug, faster to load and much harder to break. It also means I can open any page and immediately see how it works.
The simplicity is also part of the design. The pages share the same colours, typography, spacing, cards and layout patterns, so new content can be added by reusing an established system rather than inventing each page again.
Also on the bench
These are placeholder project areas for now. They can become full case studies as the work develops.
A placeholder project exploring how repeated support problems can be grouped, investigated and turned into useful product signals.
A placeholder tool for tracing requests across APIs, webhooks and external systems without losing the story of what happened.
A home for technical writing, investigation notes, scientific research and the occasional project that refuses to fit neatly into one category.
What belongs here?
Some projects begin with a product idea. Mine often begin with a confusing system, a recurring problem or a gap between what the software does and what people think it does.
The workbench is where I can show the investigation as well as the finished result: the questions, trade-offs, failed approaches and design decisions that shaped the solution.
Have an awkward problem?