Since 2014 I’ve built the unglamorous parts that make a large e-commerce platform trustworthy — payments, CI/CD, AWS infrastructure, the deploy pipeline itself. On the side I’m building Paper Trail, an open-source Go tool that mines business reports for product signals. I like systems that keep working after I hand them over.
Support teams had no shared view of which customers mattered most. I built the system that scores and ranks them automatically — from empty repository to production on AWS, solo: scoring engine, daily classification job, chat alerts, and a dashboard with preview mode so non-engineers could tune the thresholds themselves. Then I wrote the guide, trained the owners, and handed it over.
A large e-commerce platform’s daily end-to-end pipeline passed 4 of 24 jobs; a flaky, merge-blocking suite slows a whole team down. I rewrote the tests against the redesigned UIs, made data setup deterministic, fixed Stripe and PayPal checkout on ephemeral CI clones, and load-balanced the stage across parallel runners. 24/24 green, roughly twice as fast — and it stayed that way.
Every release left stale pages behind — app cache and CDN kept serving the old version. I added a post-deployment hook mechanism to the blue-green pipeline that purges caches and invalidates CloudFront on every release, eliminating that class of incidents entirely, and cut the pipeline’s retry storms and queue waits while I was in there.
A customer-feedback email programme was running blind. I built the readout: a five-stage funnel (eligible → sent → clicked → rated → text) sliced by language, message type and experiment arm, fed by a daily job capturing data the source system didn’t record — then reshaped the metrics with the product owner until they answered real questions instead of reporting totals.
The one you can read line by line. A Go CLI that mines public business white papers for repeated pain points and ranks SaaS opportunity candidates with citations back to the sources — a 13-stage pipeline across discovery, ingestion, embeddings and LLM analysis. Deliberately compliance-first: respects robots.txt, never bypasses paywalls, stores summaries rather than documents.