London, England, United Kingdom
The way software gets built is changing fast. Like a lot of engineers, I'm writing less code and shipping more. I haven't lost my head over it. LLM-assisted development takes real skill to get good results from, and for me it's meant more time on architecture and quality control, not less. I run static analysis through Claude Code hooks after every tool use, because when code arrives this fast, the verification has to be automatic. That instinct comes from operations, not theory. Products from China, campaigns for pub chains, promotional platforms with hard deadlines. Each job taught me the same thing: you verify before something ships, not after. By then the problem belongs to someone else. The tooling changed when I moved into engineering full-time; the habit carried over. A year running the SBTi website at CDP, processing emissions data for around a thousand companies, made the stakes concrete. When the data matters, you verify it properly. That verification-at-speed problem is what pulled me deep into Claude Code. I've been building the hooks and pipelines that keep quality automatic when code arrives faster than you can manually review it. I've published an MCP server to npm along the way, and I'm a regular at the London meetups, partly for the technical conversation and partly because working solo means you have to go looking for the perspectives you'd otherwise get from a team.
Production Laravel 12 applications with Filament and Livewire for client systems — campaign management with bidirectional database sync and conflict resolution, e-commerce with Stripe Cashier and WooCommerce data migration. PHPStan at maximum strictness, Pest across four layers including Playwright browser automation. Published filament-ai-forms on Packagist — AI-powered form generation using the Laravel AI SDK. Built for a client’s production system, published because it solved a problem that didn’t have a package yet. Claude Code quality pipeline: hooks enforcing PHPStan, Pint, and Rector after every tool use. Architecture tests that fail if the service layer is bypassed. The verification standard doesn’t change based on who authored the code. MCP server for Claude published on npm (TypeScript) — 22 tools with progressive disclosure design. Found and fixed a protocol-level bug in Claude Desktop along the way. CI/CD pipeline with multi-arch Docker builds and GitHub Actions for a production Grist platform on PostgreSQL.
Sole technical person building Laravel and Python systems for a promotional marketing company — campaigns for Greene King, Pokémon, Whitbread. Ran operations, then built software to fix the bottlenecks. Wild Pass (Greene King): 140K unit supply chain from China to UK, coordinating factories, QA inspectors, freight forwarders, and a deadline that didn’t move. Laravel promotional platform with 100K codes — encrypted bearer tokens, Apple and Google Wallet integration, APNS built from HTTP/2 spec (no PHP SDK existed). Carrier selection had accumulated into spreadsheets and emails — 50K shipments a year. I connected the APIs and let the software handle the comparison. Infrastructure: Grist, N8N, Prometheus, Grafana, ElasticSearch. Google Workspace admin (~20 users). Backup strategy with restic to S3.
Ran the SBTi website and coordinated its Craft CMS redevelopment — processing and publishing climate and carbon emissions data for around 1,000 companies with validated commitments across CDP, WWF, and UN Global Compact. Automated welcome card generation with Cloudinary, fixed a data streaming integration the agency couldn’t resolve.
Took a traditional print magazine online — e-commerce platform, Stripe integration handling £500K+ annually, subscription system. Over two years that more than doubled online revenue. The other half was festival infrastructure: a network spanning a kilometre, EPOS, MDM, CCTV for 10K attendees, zero downtime across four days.